Skip to main content
Rate limits control how many requests your workspace can make to the 1eye API within a given time window. They help keep the API fast and reliable for all customers.

​
Current limits

Your workspace must remain within all three limits. For example, staying below the hourly limit does not allow you to exceed the per-minute limit.

​
How limits apply

Rate limits apply at the workspace level, not per API key. All API keys in the same workspace share the same request limits. Creating additional API keys does not increase your workspace’s available capacity. For example, if two API keys in the same workspace each make 50 requests within one minute, the workspace has used its full 100-request minute limit.

​
When you hit a limit

If your workspace exceeds a rate limit, the API returns:
The response uses the rate_limit_exceeded error code.
When present, the response also includes a Retry-After header indicating how long to wait before sending another request.
Retry-After is expressed in seconds. Your integration should respect this value rather than retrying immediately.

​
Best practices

  • Respect the Retry-After header before retrying a rate-limited request
  • Avoid unnecessary duplicate requests
  • Cache responses where appropriate
  • Use pagination efficiently when retrieving large datasets
  • Monitor API Logs for unexpected spikes in request volume
  • Review Rate Limits before building high-volume integrations

​
Authentication failures

Requests that fail authentication may be subject to separate abuse protection and IP-based throttling. These requests do not consume your authenticated workspace rate limit.