Rate Limit & Quotas

You can use a certain number of requests per month, defined by your plan.

Once you go over this quota, the API returns a 429 HTTP status code, and you either need to upgrade your plan or wait until the end of the month. We also enforce a minute rate limit on the free plan: up to 10 requests per minute. If you exceed this, the API returns a 429 HTTP status code. You then have to wait until the end of the minute to make more requests.

Response Headers

We attach specific headers to every response that counts against your quota to tell you your current monthly quota and how much you have remaining in the period.

x-ratelimit-limit-quota-month: 300
x-ratelimit-remaining-quota-month: 199

On the free plan, responses also carry the per-minute limit as X-RateLimit-Limit-Quota-Minute and X-RateLimit-Remaining-Quota-Minute. Paid plans do not receive these headers.

If a subscription payment fails, your account temporarily receives a grace quota — a limited buffer of requests so your API access is not cut off right away. While the grace quota is active, requests count against the grace bucket instead of your monthly quota, and grace headers replace the monthly headers:

x-ratelimit-limit-grace-month: 30
x-ratelimit-remaining-grace-month: 12

If you have enabled overages and your monthly quota is exhausted, overage headers are sent in addition to the (exhausted) monthly headers:

x-ratelimit-limit-overage-month: 1000
x-ratelimit-remaining-overage-month: 950

In addition, successful responses from the data endpoints carry these headers:

Responses from the /status endpoint carry no cost headers at all — requests to it never count against your quota.

You can also check your remaining quota programmatically at any time via the /status endpoint — requests to it are free.