​

Errors and rate limits

Practical guidance for integrating with the QuantDesk gateway. Exact limits per route evolve — treat Swagger responses as authoritative for your deployment.

​

HTTP status codes you will see

​

V2 hardened error codes

In addition to standard HTTP codes, the V2 engine may return specific business errors in the response body or as SBF program errors:

​

Rate limiting (conceptual)

The gateway applies tiered limits on sensitive surfaces (for example auth, trading-related routes, admin, webhooks, and general API traffic). Paths under /api/ are affected differently — prefer steady request pacing over bursts.

​

Client-side discipline

• Cache stable reads where safe
• Debounce UI-driven spam
• Use bulk endpoints when documented instead of fan-out

​

Parsing errors

Prefer structured JSON error bodies when returned; log status, route, and a short correlation fingerprint — never log secrets or full JWTs.

​

Related

• Authentication
• API overview
• WebSockets overview