Understanding Our API Rate Limits

To ensure fair usage and maintain the stability of our API for all users, we've implemented rate limits. These limits restrict the number of requests you can make within a specific time frame across the whole API. Please familiarise yourself with the following rate limits:

Absence Endpoint

  • Per Second: 500 requests

  • Per Minute: 1,000 requests

  • Per Hour: 2,000 requests

  • 7-Day Period: 50,000 requests

Kudos Endpoint

  • Per Second: 500 requests

  • Per Minute: 2,000 requests

  • Per Hour: 20,000 requests

  • 7-Day Period: 300,000 requests

All other Endpoints

  • Per Second: 500 requests

  • Per Minute: 1,000 requests

  • Per Hour: 2,000 requests

  • 7-Day Period: 10,000 requests

What do these limits mean?

These numbers indicate the maximum number of API calls you can make across the whole API within the given time window. For example, for the Absence endpoint, you can make up to 500 requests in any given second, up to 1,000 requests in any given minute, and so on.

What happens if I exceed a rate limit?

If your application exceeds a rate limit, the API will return an error (typically a 429 "Too Many Requests" status code). Wait until the rate limit window resets before making further requests to that specific endpoint.

Best Practices

  • Implement throttling in your application: Design your application to avoid sending excessive requests in short periods. Implement mechanisms to queue and delay requests if necessary.

  • Monitor your usage: Keep track of your API usage to ensure you stay within the defined limits.

  • Optimize your API calls: Make efficient use of the API by retrieving only the data you need and avoiding unnecessary or redundant requests.

By understanding and adhering to these rate limits, you can help ensure a smooth and reliable experience while using our API. If you anticipate needing higher rate limits for a specific use case, please contact our Product team to discuss your requirements.