API limitations

API requests limit

The requests made to Subscription API count towards the overall API calls limit set in the Fair Use Policy or your subscription plan. There is no limit on the total number of API calls you can make.

Rate limiting

Rate limits specify the number of requests you or your application can make to Subscription API within a specific time window. There are per second and per minute time frames with different rate limits.

10 requests per second
400 requests per minute

Avoid parallel requestsWe strongly advise against making multiple requests to the API in parallel. This may cause unpredictable behavior and lead to inconsistencies in your content. We recommend that you wait for each request to finish before sending another one.

When you reach the limit of a specific time window, the API will reject the request and respond with the 429 HTTP error

JSON

{
  "request_id": "80000004-0002-fd00-b63f-84710c7967bb",
  "error_code": 10000,
  "message": "API rate limit exceeded. Please retry your request later."
}

The error response will include the Retry-After header

that tells you how many seconds you need to wait before attempting further requests. Each failed request is perfectly safe to retry. If you begin to receive 429 HTTP errors

, reduce the frequency of your requests.

CDN-level protection

In addition to these limits, a CDN-level protective layer is applied by Fastly

to protect against disruptive traffic. These limitations for uncached requests are significantly higher and are not expected to impact normal usage:

300 requests per second
2,000 requests per 10 seconds
6,000 requests per minute

Rate limiting

Rate limits specify the number of requests you or your application can make to Subscription API within a specific time window.

There are per second and per minute time frames with different rate limits.

10 requests per second

400 requests per minute