Rate Limit

Response headers describe your current rate limit for every request according to the ninth IETF draft standard This draft defines two standard fields, RateLimit-Policy and RateLimit, which provide information about active policies and remaining quota.

Header name	Description
ratelimit-policy	Lists the rate limit policies applied to your account. Each entry includes q (quota units) and w (window size in seconds).
ratelimit	Shows the remaining quota for each policy in the current response. Each entry has r (remaining quota units) and optional t (seconds until the quota window resets). Example: RateLimit: "default";r=50;t=30 means 50 requests left and the window resets in 30 seconds. When r is low, the server may soon start limiting requests.
retry-after	How many seconds you should wait before retrying when you are rate-limited (returned with HTTP 429).

The default maximum rate limit is 5 requests per second. When you exceed the limit, the server responds with a 429 error and the above headers so you can adjust your request rate.

How to avoid hitting the limit

• Reduce request rate — implement a queue mechanism or lower the number of concurrent requests per second.
• Monitor RateLimit headers — use the r and t values from the RateLimit header to adapt your sending rate.
• Use Retry-After — when you get a 429, wait the number of seconds specified before retrying.

If you need higher limits than the default, contact support to request an increase.