Rate Limits

Hostex implements rate limiting to maintain the stability and reliability of the API services. Partners are expected to respect these limits to prevent service disruptions. Exceeding these limits will result in the temporary suspension of service until the rate limit period resets.

Note: Excessive rate limit breaches may lead to extended blocks, rejection of legitimate requests, or an IP ban.

Strategies for Rate Limit Compliance

To ensure compliance with Hostex rate limits, consider the following strategies:

  1. Include both User-Agent and Hostex-Access-Token headers in your requests.
  2. Set User-Agent to your Application's name to bypass the bot detection mechanisms.
  3. Introduce a delay of one second after every 60 requests to evenly distribute calls.
  4. Employ exponential backoff when encountering rate limit errors.
  5. Always include your Access Token in request headers to establish your identity as a trusted Software Partner and avoid lower unidentified user rate limits.

Caution: A 420 User Account Issue error indicates a problem with the user account, not the rate limit. Do not resend the request; instead, advise the account holder to contact Customer Support.

Host-level Rate Limits

Receiving a 429 Too Many Requests error means you've exceeded the rate limit for your Host Account. The table below outlines the limits:

Request GranularitySpecific Account LimitAccount to Endpoint Limit
1 minute1,200 requests600 requests
5 minutes12,000 requests6,000 requests
1 hour20,000 requests10,000 requests
1 day100,000 requests50,000 requests

Host-level rate limit errors (429) do not appear in the Host Portal.

API-level Rate Limits

Most endpoints support sufficient request volumes for typical usage. However, certain endpoints have lower thresholds, which can be surpassed more easily:

EndpointRequest LimitNotes
POST /v3/availabilities120/min per hostExceeding limit results in errors for up to a minute.
POST /v3/listings/*120/min per hostExceeding limit results in errors for up to a minute.
POST /v3/reservations60/min per hostExceeding limit results in errors for up to a minute.
POST /v3/conversations/*5/5 sec per host;
1,000/hr per host		Note applicable.