Rate Limits
Learn about the rate limits we employ in our API and how to work with them.
In simplest terms, rate limits are the maximum number of API requests you can make in a given time period. Rate limits play a crucial role in ensuring the stability and performance of an API.
As you develop your integration, it's important to understand the Finix API's rate limits and ensure your systems don't programmatically create excessive requests. By controlling the number of requests your application makes, you can avoid hitting these limits and keep the performance of your application consistent and stable.
Finix can customize limits to enable high-traffic applications (or prevent abuse). If your requests are being rate-limited, reach out to your Finix point-of-contact or email Finix Support.
Rate Limits
Live Environment
These rate limits apply to our Live Environment (i.e., production).
| Operation | Limit |
|---|---|
| Writes | 100 per second |
| Reads | 100 per second |
Sandbox Environment
We also have Sandbox Rate Limits that apply for Writes and Reads. These rate limits are subject to change and are not publicly documented at this time.
Exceeding Rate Limits
Rate-limited requests return 429 HTTP Errors. If you receive a 429, your application will be unable to get the data it needs from responses to process transactions.
See Handling Rate Limits for tips on how to develop your application to work within these limits and handle 429 HTTP Errors.
If you suddenly see a rising number of requests get rate limited, please reach out to Finix Support.
Handling Rate Limits
To avoid running into rate limits, optimize your application so it makes the least amount of requests needed. By optimizing your code and monitoring usage, you can develop an application that's both efficient and effective.
Here are some strategies you can use to avoid hitting rate limits.
Exponential Backoff
To handle 429 errors, retry requests using an exponential backoff strategy. Exponential backoff gradually increases the time between retries until your requests are no longer being rate limited.
Cache Response
Caching responses can reduce the number of requests your application needs to make to process transactions.
Error Handling
If your application exceeds rate limits, make sure you have error handling in place to catch the 429 HTTP Error and handle it appropriately. Error handling can include retrying the request later or displaying an error message to the user.
Webhooks
Instead of using GET requests to retrieve data, integrate into webhooks to be programmatically alerted of responses and changes to resources you manage.