Skip to main content
Back to API List The Platform enforces rolling rate limits to restrict the number of API requests a user, application, or service can make within a dynamic timeframe. It helps prevent a single user or service from consuming disproportionate resources that could degrade the service for others. Requests are monitored against both sixty-second and one-hour limits. As long as neither limit is exceeded, the application can continue making requests. However, if the one-hour limit is breached, all further requests are blocked, even if the sixty-second limit is still within bounds. When a rate limit is exceeded, subsequent requests will fail with one of the following error messages:
  • Minute-based Limit: “You’ve exceeded the per-minute rate limit. Please wait for sometime before retrying.”
  • Hour-based Limit: “You’ve exceeded the hourly rate limit. Please wait for sometime before retrying.”

​
API Rate Limit Matrix

​
Best Practices

  • Spread out calls evenly to avoid traffic spikes.
  • Use filters to limit the data response size and avoid calls that request overlapping data.
  • When the limit has been reached, stop making API calls. Wait for the specific time period to pass. Alternatively, implement a backoff strategy where your application automatically reduces its request frequency and retries failed requests after a calculated delay.
Need a higher or custom rolling Rate Limit? Contact support.