Skip to main content
A route collection is the main unit your agent talks to in GoDizzy.

What a collection contains

Generated subdomain

GoDizzy assigns each collection a stable subdomain on godizzy.dev.

Target endpoint

Proxy rules forward requests to this upstream base URL.

Routing rules

Rules decide which requests mock and which proxy.

Collection URL

Collection URLs look like this:
https://<generated-subdomain>.godizzy.dev
The current UI does not ask the user to choose the subdomain. It is generated server-side.

Example

FieldExample
NameStripe Sandbox
Target endpointhttps://api.stripe.com
Environmentdevelopment
GoDizzy URLhttps://abc123xy.godizzy.dev

Copying a collection

Collections can be copied between environments.
1

Open the source collection

Navigate to the collection you want to duplicate.
2

Click Copy collection

Choose the target environment.
3

Confirm the copy

GoDizzy creates a new independent collection in the target environment.
The copy gets its own generated subdomain and its own future history.

What counts against plan limits

GoDizzy’s enforced plan limits are primarily based on:
  • routing rules
  • seats
A new collection matters because it includes a default routing rule, so creating a collection consumes one routing-rule slot from your organization’s allowance.
If you need more collections, the real constraint to watch is usually your routing-rule quota rather than a separate collection quota.

Deletion behavior

Deleting a collection soft-deletes it along with its rules. Its GoDizzy URL stops resolving until the collection is restored.