Data model
Environments
- Production — shared across the organization for real or shared traffic
- Development — private to the creator for experimentation and iteration
Route collections
A route collection contains:- a generated GoDizzy subdomain
- a target endpoint used by proxy rules
- an ordered set of routing rules
Routing rules
Each rule defines:- Method match — such as
GET,POST, or* - Path match — exact path, parameterized path, or wildcard
- Priority — higher numbers run first
- Action —
mockorproxy
Request flow
1
Resolve the collection
GoDizzy identifies the collection from the request subdomain.
2
Sort rules by priority
Rules are evaluated from highest priority to lowest.
3
Find the first match
The first rule whose method and path match wins.
4
Execute the action
- Mock returns the configured status, headers, body, and optional latency.
- Proxy forwards the request to the collection target endpoint.
5
Return the response
The response goes back to the caller through the same GoDizzy URL.
Path matching
Query parameters do not change path matching. Path matching is case-sensitive.
Mock vs proxy
- Mock
- Proxy
Mock rules return a configured fixture. No upstream request is made.
What changes without client rewrites
- switching a rule between mock and proxy
- editing a mock response
- changing rule priority
- adding latency to a mock rule
- updating proxy response shaping
Learn more
Environments
Production and development visibility, usage, and constraints.
Route Collections
Generated subdomains, target endpoints, and copying.
Routing Rules
Method/path matching, priority, and the default rule.
MCP
Programmatic access to environments, collections, and rules.
