Rate Limits

API Rate Limits

Guesty's Open API provides a flexible way to integrate your own solutions with the Guesty Dashboard.

In an effort to ensure that our users experience constant data flow, maintain maximum up-time and protect our platform from external threats, Guesty has maximum call limits for our Open API. These limits are set as follows:

Handling Rate Limits

To correctly address rate limits, you are required to implement a retry mechanism.

When an "HTTP 429 too many requests" response code is returned, the subsequent request should be delayed for the duration of the seconds detailed in the "Retry-after" response header.

Understanding Your API Usage

To help you better understand your API usage, Guesty also includes additional response headers in all responses returned:

• X-ratelimit-limit-<interval>: The overall requests limit set for the interval.
• X-ratelimit-remaining-<interval>: The remaining amount for requests for the interval.

These headers will be present for second/minute/hour intervals.

Guesty processes and restores your API requests at a constant rate whether you send them in bursts or at a constant rate yourself. As a result your rates quotas may remain higher than you expect (which is by design). However, if you do attempt to send more than 15 concurrent request, you’ll be instantly rate limited, and if you continue with this approach, you’ll start to see each rate limit quota decrease.

🚧

Note:

Open API rate limits on your account are shared across all API tokens. Open API rate limits are not affected by official partner integrations connected through Guesty’s Marketplace.

Best Practice

Some suggestions to assist you in the optimization of your Guesty API integrations can be found in our Help Center.