Rate limits

A rate limit is the number of API calls an app or user can make within a given time period.

Default limits

  • GET requests: 300 per 5 seconds
  • POST requests: 50 per 5 seconds

To perform bulk requests with a large number of applicants, you can call the API from a script on your server. Make sure that the script does not exceed these limits.

📘

Note

We can increase rate limits upon request. Contact our support team with your use case and explain why an increase is required.

Bad-response limit

In addition to the default limits, a separate limit applies to failed requests.

Each response with the status 400, 403, 404, or 409 counts against the limit of the app token that sent the request. If an app token receives too many such responses, all its requests, including valid ones, are rejected with 429 Too Many Requests until the limit recovers. This takes up to about 40 seconds. Other app tokens of your account are not affected.

The 429 response has the Retry-After header with the number of seconds to wait, and the following message:

Too many requests, make sure you don't retry 4xx requests (unless otherwise stated in the docs - then reduce the request rate)
🚧

Do not retry requests that return 4xx

A 4xx response means that the request itself is wrong. Retrying it unchanged does not help and only counts against the limit. Fix the cause or reduce the request rate instead.

A common cause is a scheduler that repeatedly fetches applicants by externalUserId that do not exist (404).