apaleo · Rate Limits

Apaleo Rate Limits

apaleo applies rate limiting to its REST APIs to protect platform stability. Clients that exceed the allowed request rate receive an HTTP 429 Too Many Requests response and should back off and retry. Specific per-client, per-endpoint request thresholds and windows are not publicly published as fixed numbers and are not reconciled in this artifact.

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

It captures 2 rate-limit definitions, measuring requests.

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

Tagged areas include Hospitality, PMS, Property Management, Hotels, and Rate Limiting.

2 Limits Throttle: 429
HospitalityPMSProperty ManagementHotelsRate LimitingQuotasThrottling

Limits

API Requests client
requests
see provider documentation
REST request rate limiting across the apaleo APIs; exceeding it returns 429.
Bulk / Batch Operations client
requests
see provider documentation
Bulk endpoints (e.g. units/bulk, maintenances/bulk) reduce per-call overhead for high-volume writes.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 responses and retry.
Pagination
Use pageNumber/pageSize and $count endpoints to page large result sets and avoid oversized requests.

Sources