RoomKeyPMS · Rate Limits

Roomkeypms Rate Limits

RoomKeyPMS does not publish fixed numeric per-minute/per-day request quotas. Instead it publishes operational polling guidance that functions as a de facto rate limit: pull data every 10-15 minutes, never issue parallel calls, and stagger calls across properties for multi-property integrations. Date-ranged endpoints (Reservations, Checkedout, Cancellations, Reserved) cap the fromDate/toDate window at 60 days. There is no endpoint that returns only records changed since the last call, so integrators must re-pull bounded windows on a schedule rather than consume a delta feed. RoomKeyPMS reserves the right to disable an integration's API access outright if its call pattern negatively affects server performance.

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

It captures 4 rate-limit definitions, measuring requests, days, and concurrency.

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

Tagged areas include Hospitality, Hotel Technology, PMS, Rate Limiting, and Polling.

4 Limits Throttle: not published
HospitalityHotel TechnologyPMSRate LimitingPollingGated API

Limits

Polling Frequency integration
requests
every 10-15 minutes
Documented recommended cadence for ongoing pulls against Reservation Data endpoints.
Date Range Window request
days
60
Maximum fromDate/toDate span for Reservations, Checkedout, Cancellations, and Reserved endpoints.
Parallel Calls integration
concurrency
0 (no parallel calls)
RoomKeyPMS documentation explicitly states calls should not be made in parallel.
Multi-Property Staggering account
requests
staggered, not simultaneous
Integrations covering multiple properties must stagger calls rather than firing them concurrently.

Policies

No Delta Endpoint
There is no endpoint capable of returning only records changed since the last call; integrators must re-pull bounded date-range windows.
Performance-Based Suspension
RoomKeyPMS reserves the right to disable an integration's API access if its call pattern negatively affects server performance, independent of any numeric quota.
Retry on Communication Errors
RoomKeyPMS's own guidance states retries should be implemented for times of communications issues.
Local Property Timezone
Dates and times are evaluated in the local property timezone, which matters for scheduling polling windows across multi-property, multi-timezone chains.

Sources