Rate limiting is a crucial aspect of API management, as it ensures the stability and performance of API endpoints by preventing abuse or overconsumption of resources.
We have set a rate limit for API users, permitting up to 40,000 calls per hour.
If an API user exceeds this limit, they will receive a 403 Forbidden error, indicating the client has made too many requests.
See: API Error Handling
To ensure seamless integration and prevent receiving a 403 error response due to exceeding rate limits, developers should implement the following strategies:
- Design Efficient Code: Optimize your code to minimize the number of API calls made within a minute, staying within the allowed limit. This can involve caching data, reducing redundant requests, and only requesting the data you need.
- Implement Rate Limiting Logic: Add logic in your code to track and limit the number of API calls made within a minute. This can be achieved using various techniques, such as token bucket algorithms or leaky bucket algorithms, depending on your specific use case.
- Handle Error Responses Gracefully: In the event that an error occurs, implement a retry mechanism in your code to pause and retry the API call later. This can involve exponential back-off algorithms to progressively increase the waiting time between retries and ensure that the API is not overwhelmed.
By following these best practices, development teams can prevent and handle rate limiting issues when building integrations using our APIs. This will help maintain the stability, reliability, and performance of both the API and the integrated applications, leading to a better user experience for our mutual customers and streamlined HR processes.