HotelRunner · Rate Limits

Hotelrunner Rate Limits

HotelRunner's Custom Apps documentation does not publish numeric per-minute or per-day request-rate limits for the REST or XML API. The documented operational controls are structural rather than throttling-based: inventory updates via /rooms/daily are capped at 90 dates per call, and reservation delivery failures follow a retry/timeout convention rather than a rate limit - HotelRunner expects a connecting PMS to retry a failed delivery until it succeeds or a documented timeout window (for example, 30 minutes) is reached. Update calls can also return a status of try_again, signaling the caller should retry rather than having been throttled outright.

Hotelrunner Rate Limits is the machine-readable rate-limit profile for HotelRunner on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring dates, status, minutes, and records.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Hospitality, Hotel, Channel Manager, Rate Limiting, and Quotas.

4 Limits Throttle: not published
HospitalityHotelChannel ManagerRate LimitingQuotas

Limits

Bulk Update Date Window request
dates
90
The /rooms/daily bulk update endpoint accepts at most 90 dates per room per call.
Update Retry Signal request
status
try_again response
Inventory update endpoints return status=try_again when a change should be retried rather than a numeric backoff value.
Reservation Delivery Retry Window integration
minutes
documented example: 30 minutes
PMS partners are expected to retry undelivered reservation pushes until success or a pre-defined timeout, per HotelRunner's error-handling guidance.
Reservations List Page Size request
records
per_page (default 10)
The reservations list endpoint paginates with a caller-supplied per_page and page parameter; no documented maximum page size.

Policies

Retry Until Timeout
On delivery failure (5xx range), the connecting PMS should retry sending updates until success or a pre-defined timeout is reached.
Escalate After Timeout
If delivery still fails once the timeout window elapses, HotelRunner's guidance is to escalate to partner support rather than continue silent retries.

Sources