Skip to main content

Rate Limiting

The Bilanc Metrics API implements rate limiting to ensure fair usage and maintain service reliability. Understanding these limits and implementing appropriate strategies will help you avoid disruptions to your API access.

Current Limits

  • Request Timeout: 300 seconds per request
  • Rate Limits: Implemented on a per-user basis
  • Concurrent Requests: Limited to 10 concurrent requests per user
These limits are subject to change based on service usage patterns and performance considerations.

Rate Limit Headers

When you make a request to the API, the response includes headers that provide information about your current rate limit status:

Rate Limit Exceeded Response

When you exceed the rate limit, the API returns a 429 Too Many Requests status code with the following response:

Best Practices for Handling Rate Limits

1. Monitor Rate Limit Headers

Check the rate limit headers in API responses to track your current usage and avoid hitting limits:

2. Implement Exponential Backoff for Retries

When you receive a rate limit error, use an exponential backoff strategy to retry the request:

3. Batch Requests with the Multiple Metrics Endpoint

Instead of making separate API calls for each metric, use the Multiple Metrics endpoint to reduce the number of API requests:

4. Implement Request Throttling

Limit the rate at which your application makes API requests:

5. Cache Results When Appropriate

Cache API responses to reduce the number of requests for frequently accessed data:

Requesting Rate Limit Increases

If you need higher rate limits for your application, contact Bilanc support with the following information:
  1. Your account information
  2. The specific API endpoints you’re using
  3. Your current usage patterns
  4. The reason for the rate limit increase request
  5. The expected volume of requests
We’ll review your request and determine if a rate limit increase is appropriate for your use case.