Skip to content

Rate limits

Each API token can make a limited number of requests per calendar month. The limit is tracked per token, so different tokens have separate allowances, and it resets at the start of each month.

The monthly request limit

Every token has a monthly request limit — the number of API requests it may make in a calendar month. Each successful API call counts against that token’s allowance for the current month, and the count resets to zero at the start of the next month.

You can see how much of the limit a token has used on the Settings → Developer page: each token shows a usage bar and how many requests it has left this month.

What happens when you hit the limit

Once a token reaches its monthly limit, further requests are rejected until the limit resets at the start of the next calendar month. A rejected request returns HTTP 429 Too Many Requests.

The response includes a Retry-After header telling you, in seconds, how long until the limit resets, and a JSON body describing what happened:

HTTP/1.1 429 Too Many Requests
Retry-After: 1209600
Content-Type: application/json

{
  "message": "API rate limit exceeded. You have used 1000 of 1000 requests this month."
}

Handling rate limits in your code

Watch for HTTP 429. Treat it as a signal to stop sending requests with that token until the limit resets.
Respect Retry-After. It tells you how many seconds to wait before the allowance refreshes.
Spread out your requests. If you’re approaching the limit regularly, batch or cache results rather than polling frequently.