Rate Limits

All public API endpoints are rate-limited per IP address to prevent abuse and ensure fair usage.

Limits

Response Headers

Rate limit information is not currently exposed via response headers.

Exceeding the Limit

When you exceed the rate limit, the API returns:

HTTP/1.1 429 Too Many Requests

{
  "error": "Rate limit exceeded. Please try again later."
}

Best Practices

• Cache slot queries — Available slots don’t change every second. Cache responses for 30–60 seconds on your end.
• Don’t poll aggressively — When building a date picker, fetch one week of slots at a time rather than querying every day individually.
• Implement retry logic — On a 429 response, wait at least 60 seconds before retrying.
• Use webhooks instead of polling — Rather than checking booking status by polling, subscribe to webhook events for real-time updates.