Information on rate limits for the Bila API
Rate limits are in place to ensure the stability and performance of the Bila API. They help prevent abuse and ensure fair usage for all developers.
Rate limits are applied per API key, not per user or IP address.
When a rate limit is exceeded, the API will return a 429 Too Many Requests
response. Here’s an example of the response:
To avoid hitting rate limits, follow these best practices:
Implement caching: Cache API responses when possible to reduce the number of requests.
Use bulk operations: When available, use bulk operations instead of making multiple individual requests.
Implement exponential backoff: When you receive a rate limit error, wait before retrying with an increasing delay.
Monitor your usage: Keep track of your API usage to avoid unexpected rate limit errors.
The Bila API includes rate limit information in the response headers:
Header | Description |
---|---|
X-RateLimit-Limit | The maximum number of requests allowed in the current period |
X-RateLimit-Remaining | The number of requests remaining in the current period |
X-RateLimit-Reset | The time at which the current rate limit window resets (in UTC epoch seconds) |
Here’s an example of how to handle rate limits in your code:
Different API keys may have different rate limit tiers based on your plan:
Plan | Requests per Minute | Requests per Day |
---|---|---|
Free | 60 | 10,000 |
Basic | 120 | 50,000 |
Premium | 300 | 200,000 |
Enterprise | Custom | Custom |
Consistently exceeding your rate limits may result in temporary or permanent restrictions on your API key.
If you need higher rate limits, you can:
Information on rate limits for the Bila API
Rate limits are in place to ensure the stability and performance of the Bila API. They help prevent abuse and ensure fair usage for all developers.
Rate limits are applied per API key, not per user or IP address.
When a rate limit is exceeded, the API will return a 429 Too Many Requests
response. Here’s an example of the response:
To avoid hitting rate limits, follow these best practices:
Implement caching: Cache API responses when possible to reduce the number of requests.
Use bulk operations: When available, use bulk operations instead of making multiple individual requests.
Implement exponential backoff: When you receive a rate limit error, wait before retrying with an increasing delay.
Monitor your usage: Keep track of your API usage to avoid unexpected rate limit errors.
The Bila API includes rate limit information in the response headers:
Header | Description |
---|---|
X-RateLimit-Limit | The maximum number of requests allowed in the current period |
X-RateLimit-Remaining | The number of requests remaining in the current period |
X-RateLimit-Reset | The time at which the current rate limit window resets (in UTC epoch seconds) |
Here’s an example of how to handle rate limits in your code:
Different API keys may have different rate limit tiers based on your plan:
Plan | Requests per Minute | Requests per Day |
---|---|---|
Free | 60 | 10,000 |
Basic | 120 | 50,000 |
Premium | 300 | 200,000 |
Enterprise | Custom | Custom |
Consistently exceeding your rate limits may result in temporary or permanent restrictions on your API key.
If you need higher rate limits, you can: