Skip to main content
Each host profile can make 120 requests per minute. The limit is shared by every API key on the profile, so creating more keys doesn’t raise it. At 100 bookings per page, that’s enough to page through 12,000 bookings a minute. Most integrations will never reach it.

Rate limit headers

Every authenticated response, including errors, reports where you stand in the current one-minute window:

When you hit the limit

Requests over the limit return 429 with the rate_limited error code. The Retry-After header gives the number of seconds to wait before trying again.
Wait at least Retry-After seconds, then retry. If you sync on a schedule, spread requests out rather than sending them in bursts, and use updated_since so each sync only fetches bookings that changed.

Per-IP limit

There’s also a much higher per-IP limit that protects the API from floods of unauthenticated traffic. It also returns 429 rate_limited with Retry-After, but no X-RateLimit-* headers. Normal integrations, including vendors syncing many host profiles from one server, shouldn’t reach it.
Need a higher limit? Email support@liveohana.ai with your use case.