Browse all guides

Rate Limits

Rate limits protect your workspace and keep the API fast for everyone.

Limits

Scope Limit
Per API key 60 requests / minute
Per user (across all their keys and sessions) 180 requests / minute

Both limits apply simultaneously - a single key gets up to 60 req/min, and all activity from the same user shares the 180 req/min ceiling.

When you exceed a limit

The API responds with 429 Too Many Requests and a Retry-After header telling you how many seconds to wait:

HTTP/2 429
Retry-After: 26

Best practices

  • Honor Retry-After. Sleep for at least that long before retrying, and use exponential backoff with jitter for repeated 429s.
  • Batch with pagination. Fetch with perPage=100-style pages instead of many small requests.
  • Filter server-side. Use the documented filter parameters rather than downloading everything and filtering locally.
  • Use one key per integration. Each key has its own 60 req/min budget, and per-key last_used_at makes debugging easier.
  • Cache reference data. Resources like departments, positions or lead stages change rarely - cache them for minutes, not seconds.

Need a higher limit for a specific use case? Contact us and tell us about your integration.

Questions about the API? Contact support or email support@growee.net.