Uplisting · Rate Limits

Uplisting Rate Limits

All calls to the Uplisting Public and Partner API are subject to rate limiting. Partners that exceed the limit receive an HTTP 429 Too Many Requests response. Uplisting does not publish fixed numeric thresholds for the invite- only API; specific per-partner limits are communicated during onboarding. Uplisting also expects partner API endpoints to respond within about 5 seconds, and applies a distinct reliability policy to webhook receivers.

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

It captures 4 rate-limit definitions, measuring requests, seconds, and events.

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

Tagged areas include Vacation Rental, Short-Term Rental, Channel Manager, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Vacation RentalShort-Term RentalChannel ManagerRate LimitingQuotas

Limits

Public and Partner API Requests partner
requests
not published
Rate limited; exceeding the limit returns HTTP 429. Numeric thresholds are shared during partner onboarding.
Partner Endpoint Response Time endpoint
seconds
5
Uplisting expects partner-facing endpoints to respond within about 5 seconds.
Webhook Receiver Response Time webhook
seconds
5
Webhook receiver endpoints must return a 2xx response within 5 seconds.
Webhook Consecutive Failures webhook
events
5
After 5 consecutive failed deliveries, the endpoint is auto-disabled until re-enabled.

Policies

Snapshot-Then-Webhooks
Uplisting recommends fetching an initial snapshot of bookings/availability, then using webhooks to stay in sync, rather than frequent polling.
Backoff Strategy
On a 429 response, clients should back off (exponential backoff with jitter) and retry rather than hammering the endpoint.
Webhook Auto-Disable
An endpoint that fails to respond successfully to 5 consecutive events is disabled and stops receiving events until re-enabled by the partner.

Sources