To ensure fair usage and maintain system stability, Fidel API implements rate limits based on the token bucket algorithm. This algorithm ensures a smooth and predictable distribution of requests by maintaining a bucket of tokens. Each request consumes one token from the bucket, and once the bucket is empty, further requests are temporarily rejected until new tokens are replenished at a fixed rate.
These limits define the maximum number of requests that can be made within a specific time frame. By adhering to these limits, you can optimize the performance of your application while preventing abuse or overloading of the system.
When the number of request submissions exceeds the predefined steady-state request rate and burst limits, the API will respond with an HTTP status code of 429 (Too Many Requests). It is important to handle this response appropriately in your code to ensure smooth operation of your application.
The rate limits for Fidel API are categorized based on the endpoint being accessed. Each endpoint has its own set of limits to control the number of requests allowed within a given period. Rate limits are currently being applied to the following endpoints:
| Endpoint | Burst limit | Rate limit |
|---|---|---|
| Create Card | 3 | 1 per second |
If you anticipate requiring higher rate limits due to specific business needs, please reach out to our support team. We will evaluate your requirements and assist you in finding a suitable solution.