Rate limiting errors

When your application makes too many requests in a short period, the API returns 429 Too Many Requests. This protects our infrastructure and ensures fair and consistent service usage across all API consumers.

The API applies rate limiting per second across all API routes.

Handling 429 responses

If you receive a 429 Too Many Requests status code:

• Wait ~ 1 second before retrying.
• Reduce parallel requests to avoid hitting the limit again.
• Use exponential backoff when retrying failed requests.

Recommendations to avoid hitting rate limits

• Use the bulk API to combine multiple operations into a single call.
• Throttle or batch requests instead of sending them all at once.
• Queue requests to limit concurrency.
• Cache repeated results to minimize unnecessary API calls.