Register your integration in the Mews Marketplace and obtain a Client Token and Access Token; all Connector API requests require both Client Token and Access Token fields in the JSON request body
Query the reservations endpoint using the Access Token to retrieve reservations within scope, applying filters such as date range and reservation state; use pagination for large result sets
Subscribe to reservation-related Webhook events to receive real-time notifications when bookings are created, modified, or cancelled rather than polling
Validate inbound webhook authenticity by checking the shared secret token appended to your webhook endpoint URL before processing any payload
Post charges to a guest folio by calling the order or accounting item endpoints with the reservation identifier and the charge details
Use Portfolio Access Tokens if your integration manages multiple Mews properties to query across the entire portfolio in a single API call
Known gotchas
The Mews Connector API requires both Client Token and Access Token in every request body, not just in headers; missing either field returns an authentication error even if credentials are otherwise correct
Webhook endpoints must return an HTTP 200, 202, or 204 within a short timeout; slow responses or non-2xx codes cause Mews to retry delivery, potentially creating duplicate processing
Mews uses a data model where a booking is a container for multiple reservations, each covering one room; code that expects a single reservation object per booking will miscount multi-room stays
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp