Skip to main content
The Zeeg API enforces rate limits to ensure fair usage and platform stability for all integrations. Limits may vary by endpoint and subscription plan.

​
Handling Rate Limits

When you exceed the rate limit, the API returns a 429 Too Many Requests response. Wait before retrying — the response will indicate when you can send the next request.

​
Retry Strategy

Implement exponential backoff when you receive a 429 response. Wait progressively longer between retries to avoid overwhelming the API:
  1. Wait 1 second, then retry.
  2. If still rate-limited, wait 2 seconds, then retry.
  3. Continue doubling the wait time up to a reasonable maximum (e.g., 60 seconds).
Add a small random jitter to each wait interval to prevent multiple clients from retrying in sync.

​
Best Practices

  • Cache responses when possible to reduce unnecessary API calls.
  • Use webhooks instead of polling for event updates such as booking changes or cancellations.
  • Use pagination with reasonable page sizes rather than fetching large datasets in a single request.
  • Spread requests over time rather than sending bursts of parallel requests to the same endpoint.

​
Need Higher Limits?

If your integration requires higher rate limits, contact support@zeeg.me with details about your use case.
Last modified on April 4, 2026