Rate limits
What are Rate Limits and Why are They Needed?
Rate limits control the number of API requests that can be made within a specific time frame. By enforcing these limits, we prevent overloading the system, which ensures fair usage for all clients and maintains the overall performance and stability of the platform. This approach helps protect our infrastructure from potential abuse and ensures that all users have a consistent and reliable experience.
Getting Started with Rate Limits
Understanding and managing rate limits is crucial to ensuring optimal performance and stability when using Lexer APIs. Rate limits help maintain the efficiency of our platform, ensuring it remains quick to load and reliable for all users.
To make sure our platform is quick to load and remains stable for everyone, all Lexer APIs are rate limited. We ask developers to use industry-standard techniques for limiting calls, caching results, and re-trying requests responsibly.
The nuts and bolts
- Our rate limits are defined as the number of requests per minute permitted before returning a [.code]429 Too Many requests[.code] response code to the requester.
- Certain rate limits are applied to API keys to manage traffic efficiently. It may be increased depending on your use cases. Please your Success Manager to discuss it further. Error 429 will indicate an exceeded rate limit (for more information about our API tokens, take a look at our Authentication and API token creation article).
- Although the rate limits are tied to an API token, it is not advised that you create additional API tokens to increase capacity.
Do you need additional capacity?
If the API rate limits are too restrictive, we can grant additional capacity for your use cases by contacting our Support team at support@lexer.io. Or consider the bulk alternatives such as AWS S3 and SFTP.
Any questions?
If you would like to know more about our rate limits or have any questions about our APIs, please contact our Support team or your Success Manager.
