Rate Limits

Understand how ComplyCube rate limiting works.

ComplyCube’s API enforces the following maximum request rates:

• Live environment: up to 10 requests per second.

• Test (Sandbox) environment: up to 5 requests per second.

Requests that exceed these limits may be throttled or temporarily blocked.

Any request that exceeds the allowed rate will receive a 429 Too Many Requests response.

You should implement suitable error handling for 429 errors. Using an exponential backoff strategy with random jitter is the recommended approach to safely retry requests and avoid repeated throttling.

Avoiding the limit

To help prevent reaching rate limits, consider the following best practices:

• Run non-essential or routine batch jobs outside of peak hours.

• Throttle or limit the frequency of batch jobs.

• Implement exponential backoff for retries, starting with a 30-second delay.

• Prioritize requests that are essential to verifying active clients.

• Use webhooks instead of polling our API for updates.