Rate limits and backoff

​

Response headers

​

Handling flow

​

Client recommendations

• Do not hard-code a quota that is not defined by your effective response headers.
• Limit concurrent requests per API key.
• Share rate-limit state across workers that use the same key.
• Add random jitter to avoid synchronized retries.
• Stop retries when the operation’s budget is exhausted.
• Separate retry handling from business validation queues.
• Do not rotate keys merely to bypass rate limits.

​

Example

HTTP/1.1 429 Too Many Requests
RateLimit-Policy: ...
RateLimit: ...
Retry-After: 60
X-Request-ID: 018f3d9a-7dfb-7a23-b4b4-9f7e4b19d4b4