Rate Limits

All CloudCruise API endpoints are subject to the following global rate limits:

Rate limits are tracked per API key. If multiple time windows are exceeded simultaneously, the most restrictive limit applies.

429 Response

When you exceed a rate limit, you’ll receive a 429 Too Many Requests response:

{
  "statusCode": 429,
  "error": "Too Many Requests",
  "message": "Too Many Requests",
  "limit": 500,
  "retryAfterSeconds": 1
}

Field	Description
`limit`	Maximum requests allowed in the violated time window
`retryAfterSeconds`	Seconds to wait before retrying

Use webhooks instead of polling. Webhooks notify your server immediately when a run completes, eliminating the need for polling the run results endpoint.
Use our SDKs. The TypeScript and Python SDKs use server-sent events for real-time updates, avoiding polling entirely.
Implement exponential backoff. If you receive a 429, wait for retryAfterSeconds before retrying and increase the delay on subsequent failures.