Rate Limits & Quotas

Overview

Que applies default rate limits to all API keys.
Rate limits ensure the service remains stable and fair for all teams using the platform.

Each request you send (to sign, verify, or upload assets) counts toward your key’s quota. Most projects never hit these limits, but heavy usage workloads may need adjustments.

Default Limits

By default:

• Per-key quotas are applied over short windows (seconds to minutes).
• If your key exceeds the quota, requests will fail with a 429 Too Many Requests error.
• The error response may include a Retry-After header indicating when you can safely retry.

Example 429 Response

{
  "type": "about:blank",
  "title": "rate_limited",
  "status": 429,
  "code": "rate_limited",
  "detail": "try again in 5000 ms",
  "details": {
    "try_again_in_ms": 5000
  }
}

Best Practices

• Batch smaller assets when possible. Each upload, verify, or sign call is counted separately.
• Implement retry logic. Use the Retry-After value to decide when to retry.
• Monitor usage. Use metrics in the developer dashboard or your own logging to observe request volume.

Future Quotas

While Que is in free beta, limits are meant as fair use caps, not billing triggers.
In the future, rate-limit tiers will align with pricing plans:

• Starter: light usage, generous free quota
• Pro: higher sustained throughput for commercial use
• Enterprise: custom SLAs and throughput guarantees

We’ll update this page