.svg?fit=max&auto=format&n=9voKLLkajreclhp4&q=85&s=321632804eda4b3cff044941f9ccadda)
The Zeeg API enforces rate limits to ensure fair usage and platform stability for all integrations. Limits may vary by endpoint and subscription plan.Documentation Index
Fetch the complete documentation index at: https://developer.zeeg.me/llms.txt
Use this file to discover all available pages before exploring further.
Handling Rate Limits
When you exceed the rate limit, the API returns a429 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 a429 response. Wait progressively longer between retries to avoid overwhelming the API:
- Wait 1 second, then retry.
- If still rate-limited, wait 2 seconds, then retry.
- Continue doubling the wait time up to a reasonable maximum (e.g., 60 seconds).
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.