Rate limit headers
The API returns rate limit information in the response headers for every request:Example response headers
Handling rate limits
A basic technique for integrations to gracefully handle limiting is to watch for429 status codes and build in a retry mechanism. The retry mechanism should follow an exponential backoff schedule to reduce request volume when necessary.
When you exceed your rate limit, the API will return a 429 error with a message indicating how long to wait before retrying. Use the Retry-After header to determine when to make your next request.
Example error response
When rate limited, you’ll receive a response like:Retry-After header indicating how many seconds to wait.