Rate Limiting

The ZopNight API enforces rate limits per organization to ensure fair usage and service stability.

How It Works

Rate limiting is applied at the gateway level, tracked per organization using Redis. Limits are based on the number of requests per minute.

Rate Limit Response

When the rate limit is exceeded, the API returns a 429 status:

HTTP 429 Too Many Requests

{
  "error": {
    "message": "rate limit exceeded"
  }
}

Best Practices

• Implement exponential backoff — when you receive a 429 response, wait before retrying. Double the wait time with each retry (1s, 2s, 4s, etc.).
• Cache responses — avoid redundant API calls by caching resource lists, schedules, and other data that changes infrequently.
• Use batch endpoints — fetch multiple resources with /resources/by-ids instead of individual GET requests.
• Avoid polling — use reasonable intervals when polling for action status or refresh completion.