Rate Limit Policy
- The limit is counted per customer, not per API key. Every API key on the same customer account shares one limit.
- All endpoints draw from the same shared limit. For example, 15 proxy search requests and 5 service search requests in the same second together use the full 20.
- The limit is measured over a rolling one-second window.
- Protect the API from excessive traffic
- Ensure fair access for all users
- Maintain reliable service performance
Endpoint-Specific Limits
These endpoints have limits in addition to the default:
Every other Public API endpoint uses the default limit of 20 requests per second.
Rate Limit Exceeded Response
If you exceed the rate limit, you’ll receive a429 Too Many Requests response with a body like:
429, wait briefly and retry. Exponential backoff (for example 1s, 2s, then 4s) is recommended. To avoid hitting the limit, spread requests evenly over time instead of sending them in bursts, and limit how many requests your integration runs in parallel.
Increase Your Rate Limit
Need Higher Limits?
We can raise rate limits for individual customers.Contact [email protected] with a fair reason for the increase, such as your use case and the request volume you expect.

