Mews

What you can build

• Turn a checkout into a cleaning task

  Watch ServiceOrderUpdated for a reservation reaching Processed, then propose a housekeeping task with a deadline before the next arrival on that space.

  With Clean Sequence, Room Ready

• Mark the space ready once inspected

  When a Dirty space has no in-house guest and the inspection is logged, propose resources/update to Inspected for the supervisor to approve.

  With Room Ready, DND Check

• Answer a guest message with the reservation in view

  Subscribe to MessageAdded, read the thread and the reservation behind it, and propose a reply or a department task for approval.

  With Guest Requests, First Response

• Prepare a late checkout

  Read reservations ending today, check the space's next arrival through its occupancy state, and propose a reservation interval change where the space is free.

  With Late Checkout

Requirements

• A Mews enterprise that creates the integration and shares its AccessToken; demo and production need separate token sets
• A ClientToken from Mews; production tokens follow the Mews certification form and a review of the operations you use
• An HTTPS endpoint that answers webhook POSTs within 5 seconds; Mews registers it through its support team
• The demo environment at api.mews-demo.com for development; production is api.mews.com

Authentication

A ClientToken that Mews issues to your application after its certification process, plus an AccessToken generated for each enterprise (property) that connects, both sent in the JSON body of every request together with a Client name and version.

Limits

• 200 requests per AccessToken within 30 seconds, measured on a sliding window, in both demo and production; excess returns 429
• One General Webhooks endpoint and one Integration Webhooks endpoint per integration client
• Webhook payloads carry entity ids only; you fetch the entity afterwards, and delivery can lag by several minutes
• A webhook that fails or takes longer than 5 seconds is re-sent after a few minutes and eventually discarded

Questions and answers

Does the Mews Connector API use GET requests?

No. Every operation is an HTTP POST with a JSON body, and the body carries the credentials: ClientToken, AccessToken, and Client. The demo platform is api.mews-demo.com and production is api.mews.com; each environment needs its own tokens.

What does a Mews webhook contain?

An EnterpriseId, an IntegrationId, and an Events array. Each event has a Discriminator such as ServiceOrderUpdated or ResourceUpdated and a Value holding the entity Id. You then call the matching getAll operation to read the entity; Mews recommends one call when several events name the same entity.

What is the request limit on the Mews Connector API?

Mews enforces 200 requests per AccessToken within 30 seconds on a sliding window, in both demo and production. When you exceed it the platform returns 429 Too Many Requests, and the client is expected to back off.