API Rate Limiting
Our HTTP API has a rate limiting mechanism in place to ensure fair usage of the API and prevent abuse. The rate limits are determined by the type of account you have with us:
Enterprise Account
For Enterprise accounts, the default rate limit is set at 200 requests per second per API key and 2 requests per second per user_account
. This allows for high-frequency usage of the API while still maintaining a fair balance for all users.
The user_account
is defined as a user address and a limit exists to stop abuse by a single account. The per user_account
rate-limit is configurable.
It's important to keep in mind that these rate limits are subject to change and may be adjusted based on the usage patterns of our API. If you require a higher rate limit, please reach out to our support team for more information on how to upgrade your account ([email protected]).
Free Account
For Free accounts, the rate limit is set at 20 requests per second per API key. This allows for a more limited usage of the API, but still enough for basic integration and testing.
Rate Limited Response
In the case that you exceed the rate limit, the API will return a 429 "Too Many Requests" response. With the following JSON payloads:
- API key rate limit exceeded
{"error":"API key call limit exceeded"}
- Per user
user_account rate limit exceeded
{"error":"User call limit exceeded"}
If you receive this response, it's recommended to implement an exponential backoff algorithm in your client to handle the rate limiting. This will help to reduce the number of requests made during a limited period and ensure that your client does not repeatedly hit the rate limit.
Updated 12 months ago