Mews · Rate Limits

Mews Systems Rate Limits

The Mews Connector API enforces rate limiting scoped per AccessToken (per connected property/enterprise), not per ClientToken or per IP. Both the demo and production environments allow up to 200 requests per AccessToken within a rolling 30-second window. The limiter uses a sliding window anchored to the first request in a burst rather than fixed clock buckets. When the limit is exceeded the API returns 429 Too Many Requests with a Retry-After header indicating how long to wait; Mews advises client-side rate limiting and exponential backoff. In rare cases where a request places heavy demand on the system the API may return 408 Request Timeout. Mews notes the request count and time window may change without prior notice.

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

It captures 3 rate-limit definitions, measuring requests_per_second and varies.

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

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

3 Limits Throttle: 429
Rate LimitingHospitalityProperty ManagementPMS

Limits

Connector API requests (production) account
requests_per_second · second
200
200 requests per AccessToken within any rolling 30-second window (sliding window anchored to the first request in a burst).
Connector API requests (demo / sandbox) account
requests_per_second · second
200
Demo environment (api.mews-demo.com) enforces the same 200 requests per AccessToken per 30 seconds as production.
Booking Engine (Distributor) API requests account
varies
shares the Mews API platform limiter; expect AccessToken-scoped throttling with 429 + Retry-After
Front-end client-facing API on the same api.mews.com platform; treat the 200-per-30s AccessToken budget as the baseline.

Policies

Sliding window
The 30-second window is anchored to the first request in a burst, not to clock boundaries, so spreading requests evenly avoids tripping the limiter.
Per-AccessToken scope
Limits are bound to the AccessToken (the connection to a specific property/enterprise). Multi-property integrations using Portfolio Access Tokens should account for shared budget across that token.
Retry-After backoff
On 429, read the Retry-After response header and wait the indicated duration before retrying; fall back to exponential backoff if the header is absent.
Client-side rate limiting
Mews recommends implementing client-side rate limiting so the integration does not keep sending requests after receiving a 429.
Subject to change
Mews states the number of requests and the time window can change without prior notice; integrations must handle 429 gracefully rather than hard-coding assumptions.

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/mews-systems-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.