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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-07-03.
Written by API Evangelist on 2026-07-03 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/uplisting-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.