Environments
Each Quiddly tenant runs in one or more isolated environments. API hostnames
are usually {tenant}-{country}-api.{domain} for production and
{tenant}-{country}-test-api.{domain} for sandbox.
| Environment | Purpose | Example host |
|---|---|---|
| Production | Live data, real money. | acme-se-api.quiddly.com |
| Sandbox | Seed data, safe to break. | acme-se-test-api.quiddly.com |
The sandbox tenant is identical in shape to production: same endpoints, same auth flows. Service accounts and credentials are scoped to a single environment - you cannot use a production token against sandbox or vice versa.
Pointing the interactive reference at sandbox
Section titled “Pointing the interactive reference at sandbox”The reference defaults to this tenant’s host. To
try requests against your sandbox without leaving the portal, open the
sandbox tenant’s /developers/reference URL directly.
Rate limits
Section titled “Rate limits”Quiddly does not currently enforce a hard request-per-second limit, but may
introduce rate limits in the future - design clients to back off and retry on
429 Too Many Requests. The backend does enforce per-request statement timeouts
in PostgreSQL (60 seconds by default); long-running list operations return 504
with {"error": "Query timed out."} - paginate them.