Mews API
Mews is a cloud-native hospitality platform that unifies property management, point-of-sale, revenue management, and embedded payments for hotels and accommodation providers. An API lets you programmatically pull reservations, guest profiles, spaces, rate plans, accounting items, and payments—and push updates like new bookings, check-ins, charges, and order items back into Mews Operations.
What is Mews?
Mews is a cloud-native hospitality operating system that unifies property management, point-of-sale, revenue management, and embedded payments so hotels and accommodation providers can run reservations, the guest journey, operations, and back-office finance from a single platform. Properties use Mews to manage bookings, check-in and check-out, housekeeping, billing, and reporting, and extend their stack through the Mews Marketplace of 1,000+ hospitality integrations built on the Mews Open API.
Core product areas include:
- Property Management System (reservations, guest intelligence, housekeeping, groups & events, upsells, accounting & billing, booking engine, guest check-in)
- Point-of-Sale (ePOS for food & beverage operations with embedded payments)
- Revenue Management System (dynamic pricing, demand forecasting and controls)
- Payments (tokenization, automated reconciliation, multicurrency support, payment terminals)
- Open API, Marketplace, and Data & Reporting
Common data entities:
- Reservations, Groups, Availability Blocks, Vouchers
- Customers (guest profiles), Companies, Loyalty memberships
- Spaces (rooms/resources), Space Categories, Resource Blocks, Housekeeping tasks
- Rates, Rate Groups, Restrictions, Products, Order Items
- Bills, Accounting Items, Payments, Outlet Items (POS)
The Mews Integration Challenge
Mews exposes a public Connector API, but turning it into reliable, property-spanning automation still presents real obstacles:
- Dual-token authentication: every request needs both a ClientToken (your application) and a property-specific AccessToken, so multi-property automation means managing and rotating many credential pairs
- Partner certification gates: production ClientTokens and the Marketplace require going through Mews partner onboarding and certification before broad API access is granted
- High-volume polling and timestamps: change-tracking by UTC timestamps across reservations, items, and payments requires careful pagination and cursoring to stay in sync without missing updates
- Property-specific configuration: rate groups, space categories, products, and tax/accounting setup vary per enterprise and per property, so generic integrations break across tenants
- Payments and financial precision: charges, refunds, and reconciliation through embedded Mews Payments require idempotency and exact accounting-item handling
- Coverage gaps: not every Operations workflow is exposed identically, and webhook events versus polling differ by entity and API version
How Supergood Creates Mews APIs
Supergood wraps the Mews Connector API and authenticated Operations flows to deliver a resilient, normalized API layer for your properties—handling token management, pagination, and configuration drift so you integrate once.
- Manages ClientToken and per-property AccessToken pairs securely with rotation and scoped access
- Handles timestamp-based change tracking, pagination, and cursoring so you stay in sync across reservations, items, and payments
- Normalizes responses across reservations, customers, spaces, rates, accounting, and payments so you integrate once and rely on consistent objects
- Aligns with each property's rate groups, space categories, products, and tax configuration for accurate, compliant access
Use Mews with AI agents: Mews MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your properties, modules, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready Mews adapter tailored to your property configuration and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Mews evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a Mews property using ClientToken and property-specific AccessToken and establish a session for downstream calls.
Reservations
/reservationsList reservations with filters for property, state, stay dates, and updated-since timestamp for change tracking.
Reservations
/create_reservationCreate a new reservation against a space category and rate plan, including guest, dates, and product selections.
Customers
/customersRetrieve guest profiles and company records with contact, loyalty, and classification data.
Billing
/billsPull bills, accounting items, and order items across reservations and POS outlets for reconciliation.
Payments
/create_paymentPost a charge, refund, or payment against a bill through embedded Mews Payments with idempotency handling.
Use Cases
Sync reservations and guest data into your warehouse
- Pull reservations, groups, and availability blocks with updated-since cursoring into a single warehouse - Reconcile customer and company profiles across properties for a unified guest 360 - Stream reservation state changes to downstream CRM, marketing, and BI tools
Automate the check-in and guest journey
- Create and update reservations, assign spaces, and trigger check-in without portal clicks - Push pre-arrival upsells and product orders back into Mews - Surface housekeeping task status and room readiness to operations dashboards
Reconcile billing and payments
- Sync bills, accounting items, and order items from PMS and POS into general ledger and AR systems - Post charges, refunds, and payments through embedded Mews Payments with idempotency - Match multicurrency settlements and reconciliation reports against finance systems
Drive revenue and rate automation
- Pull rates, rate groups, restrictions, and availability for dynamic pricing tools - Push rate and restriction updates back into Mews from a revenue management engine - Feed occupancy and demand signals to forecasting and channel-management systems
Technical Specifications
Authentication
ClientToken plus property-specific AccessToken handled in a managed, rotating session
Connectivity
Mews Connector API plus authenticated Operations flows surfaced through a single normalized layer
Response format
Normalized JSON across reservations, customers, spaces, rates, accounting, and payments objects
Rate limits
Adaptive throttling tuned per property to respect Mews-side request limits and avoid contention
Session management
Automatic token management, AccessToken rotation, and credential vaulting per property
Data freshness
Near real-time pulls via updated-since timestamp tracking with optional scheduled batch syncs
Security
Encrypted credential vault, scoped tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for reservation, item, and payment changes where exposed, with polling fallback
Latency
Sub-second reads on cached entities; multi-second writes when posting reservations, charges, and payments
Throughput
Horizontally scaled workers sized to multi-property reservation and POS volume
Reliability
Retry, backoff, and idempotency keys for reservation, billing, and payment transactions
Adaptation
Continuous monitoring of Mews Connector API versions, Marketplace changes, and per-property configuration drift
Frequently asked questions
Yes. Mews offers the public Connector API for partners. Supergood layers on top of it to manage dual-token authentication, pagination, and per-property configuration, and to normalize responses so you integrate once across all your properties.
Supergood works with your existing property AccessTokens and authenticated access. Where production ClientTokens or Marketplace listing require Mews partner certification, we operate within your entitlements rather than requiring you to rebuild that onboarding.
Yes. Supergood manages a ClientToken plus per-property AccessToken for each property and presents a single normalized API across the portfolio, so chain- and brand-level automation works without juggling credential pairs by hand.
Yes. Order items from the ePOS and charges, refunds, and reconciliation through embedded Mews Payments are exposed alongside reservations and accounting items on the same normalized surface.
Each property is profiled against its rate groups, space categories, products, and tax setup. Supergood preserves property-specific fields and configuration rather than forcing a generic schema across tenants.