Rate Limits

Overview

API rate limits protect platform stability and fairness across accounts.

Best Practices

• Cache read-heavy responses when possible.
• Use exponential backoff for retriable failures.
• Avoid burst traffic from cron jobs at the exact same minute.

Handling Limit Responses

If you receive a rate-limit response, wait before retrying and reduce request concurrency.

Example 429 Response

A throttled endpoint may return:

{
  "detail": "Rate limit exceeded. Try again in 23 seconds."
}

Response Shape Notes

• Error responses use a detail field with a human-readable message.
• Wait duration is expressed in seconds in the message.
• Retry after waiting, and reduce burst/concurrency to prevent repeated 429s.