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.
Limits
Policies
Sources
- https://apaleo.dev/guides/api/overview.html
- https://apaleo.dev/guides/webhook/best-practices.html
- https://api.apaleo.com/swagger/index.html
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.