Skip to main content
A route collection is the core building block of GoDizzy. It gives your agent a single, stable URL to call. Everything else — whether a request gets mocked, proxied, injected with latency, or reshaped — is determined by the routing rules inside the collection.

​
What a collection contains

Every collection has three parts:

Subdomain

A unique identifier that forms your gateway URL: <subdomain>.godizzy.dev. This URL never changes regardless of what your rules are doing.

Target endpoint

The upstream URL that proxy rules forward requests to. This is the real API you want to reach when you’re not mocking.

Routing rules

The ordered set of rules that decide how each incoming request is handled — matched by HTTP method and path, then either mocked or proxied.

​
The gateway URL

Each collection gets a subdomain-based URL in the format: 
https://<subdomain>.godizzy.dev
For example, a collection with the subdomain payments-sandbox would be reachable at: 
https://payments-sandbox.godizzy.dev
Your agent calls this URL. GoDizzy intercepts each request, evaluates the routing rules, and either returns a mock response or forwards the request to your target endpoint — all without your agent knowing or caring which mode is active.

​
Example: Stripe sandbox collection

Here’s what a typical collection looks like for sandboxing the Stripe API:
FieldValue
NameStripe Sandbox
Subdomainpayments-sandbox
Target endpointhttps://api.stripe.com
EnvironmentDevelopment
With this collection in place, a request from your agent to: 
POST https://payments-sandbox.godizzy.dev/v1/charges
…will be evaluated against the collection’s routing rules. If the matching rule is set to mock, your agent gets back a fixture. If it’s set to proxy, GoDizzy forwards the request to https://api.stripe.com/v1/charges. The agent’s code stays the same either way.

​
Copying a collection across environments

You can copy a collection from one environment to another directly from the dashboard. This is useful when you’ve built and tested a configuration in development and want to promote it to staging or production.
1

Open the collection

Navigate to the collection you want to copy.
2

Click Copy collection

Select the target environment from the list of environments you have access to.
3

Confirm

GoDizzy creates a fully independent duplicate in the target environment — including all routing rules and mock responses. You can rename it after copying.
The copied collection is completely independent. Changes to the original don’t affect the copy, and vice versa. The copy gets its own subdomain URL.

​
Collection limits

Collections in your production environment count toward your plan’s collection limit. Collections in staging and development environments do not count toward the limit.
PlanCollection limit
Free1
Starter5
Pro25
Business100
If you’re experimenting with a new configuration, build it in your development environment first. It won’t touch your production collection count until you’re ready to promote it.

​
Soft deletion

Deleting a collection soft-deletes it along with all of its routing rules. Requests to the collection’s subdomain will return a 404 after deletion. The data is preserved and recoverable — contact support if you need to restore a deleted collection.