Mews website screenshot

Mews

Mews is a cloud-native hospitality cloud and property management system (PMS) headquartered in Prague, Czech Republic that powers reservations, operations, payments, point of sale, revenue management, and distribution for more than 15,000 hospitality properties globally. The Mews Open API surface is organised into five product APIs — the general-purpose Connector API for partners working with Mews Operations data, the Channel Manager API for two-way distribution with OTAs and channel managers, the Booking Engine API for guest-facing reservation creation, the POS API for point-of-sale integrations, and the Loyalty Partner reverse API for membership systems. Mews also runs a marketplace of more than 1,000 hospitality integrations.

5 APIs 12 Features
HospitalityHotelProperty ManagementPMSReservationsBookingsTravelPaymentsPoint of SaleChannel ManagerBooking Engine

APIs

Mews Connector API

The Mews Connector API is the general-purpose Open API for Mews Operations. Partners use it to access enterprise configuration, reservations, customers, bills, payments, account...

Mews Channel Manager API

The Mews Channel Manager API is the two-way distribution surface between Mews and channel managers, online travel agents (OTAs), and other bulk sales channels. Mews pushes avail...

Mews Booking Engine API

The Mews Booking Engine API (historically published as the Distributor API and still served from the /api/distributor/v1 path) lets developers build custom guest-facing booking ...

Mews POS API

The Mews POS API gives partner point-of-sale systems real-time access to Mews POS data and services so that food and beverage, retail, and ancillary outlets can post charges to ...

Mews Loyalty Partner API

The Mews Loyalty Partner API is a reverse API — Mews calls endpoints that the loyalty provider hosts — used to integrate third-party loyalty and membership programs with Mews Op...

Collections

Pricing Plans

Rate Limits

Mews Systems Rate Limits

3 limits

RATE LIMITS

FinOps

Features

Cloud-Native Property Management System

Reservation management, group bookings, guest check-in/out, housekeeping, billing, and accounting in a single hosted PMS

Point of Sale (POS)

Embedded POS for hotel restaurants, bars, and ancillary outlets with charge posting to guest folios

Revenue Management System (RMS)

Dynamic pricing, demand forecasting, and portfolio/group pricing with AI assistance

Integrated Payments

Tokenization, multicurrency, automated reconciliation, and certified payment terminals

Open API Surface

Five product APIs — Connector, Channel Manager, Booking Engine, POS, and Loyalty Partner — for partners and custom integrations

Webhook Events

Connector API events feed for near real-time integration with reservation, customer, and billing state changes

Portfolio Access Tokens

Single-token access across multiple properties for chain and enterprise integrations

Mews Marketplace

1,000+ certified hospitality integrations spanning channel managers, OTAs, POS, payments, guest experience, BI, and operations

Booking Engine

Direct-booking widgets and websites powered by the Booking Engine API

Business Intelligence and Analytics

Reporting, KPI dashboards, and data exports for revenue, operations, and guest data

Security and Compliance

SOC 2, ISO, and PCI DSS certified hosting and processing

Multi-Property and Multi-Brand Support

Single Mews account spans many properties, brands, and legal entities under chain or enterprise structures

Use Cases

Kiosk and Self Check-In

Build self-service kiosks and mobile check-in flows on top of the Connector API

Custom Booking Engine

Power direct-booking widgets and white-label websites with the Booking Engine API

OTA and Channel Manager Distribution

Two-way sync of availability, rates, inventory, and reservations between Mews and OTAs via the Channel Manager API

Point of Sale Integration

Post charges from restaurant, retail, spa, and activity POS to guest folios via the POS API

Loyalty Program Integration

Plug a loyalty or membership program into the Mews reservation and folio lifecycle via the Loyalty Partner API

Business Intelligence and Reporting

Pull reservation, revenue, and operations data into BI tools and data warehouses

Accounting and Finance Automation

Reconcile bills, payments, and accounting categories with general-ledger and ERP systems

Guest Experience and Upsell

Deliver pre-arrival upsell, in-stay messaging, and guest-app experiences using Connector API data and events

Operations and Housekeeping

Drive housekeeping, maintenance, and task workflows with real-time room and reservation state

Fiscalization and Tax Reporting

Report e-invoices to government tax authorities using the open-source Mews Fiscalizations .NET library

Integrations

Online Travel Agents

Booking.com, Expedia, Airbnb, and other OTAs via certified channel managers using the Channel Manager API

Channel Managers

SiteMinder, Cloudbeds, RateGain, D-EDGE and other channel managers via the Channel Manager API

Payment Processors

Mews Payments plus integrations with Adyen, Stripe, and regional acquirers

Point of Sale Systems

Mews POS plus third-party POS vendors integrated via the POS API

Business Intelligence

Connector API feeds into Power BI, Tableau, Looker, and hospitality BI tools like HotelIQ and Demand Calendar

Guest Experience Apps

Mobile check-in, messaging, upsell, and concierge apps built on the Connector API

Revenue Management

Mews RMS plus third-party RMS vendors like Duetto, IDeaS, and Atomize integrated via the Connector API

Accounting and ERP

General-ledger and ERP integrations including Xero, QuickBooks, NetSuite, and SAP via the Connector API

Door Locks and IoT

Smart-lock and in-room device vendors integrated through the Connector API

Fiscalization Authorities

Government e-invoice and fiscal reporting via the open-source Mews Fiscalizations .NET library

Solutions

Independent Hotels

PMS, POS, payments, and booking engine for single-property independent hotels

Hotel Chains and Enterprise

Multi-property, multi-brand operations with portfolio access tokens and central reporting

Hostels

Bed-level inventory, group bookings, and self-service flows for hostels

Serviced Apartments and Extended Stay

Long-stay billing, recurring charges, and apartment-style inventory

Motels and Limited Service

Streamlined operations and self-service check-in for limited-service properties

Semantic Vocabularies

Mews Systems Booking Engine Context

18 classes · 0 properties

JSON-LD

Mews Systems Connector Billing Context

9 classes · 0 properties

JSON-LD

Mews Systems Connector Configuration Context

1 classes · 0 properties

JSON-LD

Mews Systems Connector Customers Context

6 classes · 0 properties

JSON-LD

Mews Systems Connector Operations Context

8 classes · 0 properties

JSON-LD

Mews Systems Connector Payments Context

4 classes · 0 properties

JSON-LD

Mews Systems Connector Pos Context

3 classes · 0 properties

JSON-LD

Mews Systems Connector Reservations Context

4 classes · 0 properties

JSON-LD

Mews Systems Connector Resources Context

2 classes · 0 properties

JSON-LD

Mews Systems Connector Services Context

3 classes · 0 properties

JSON-LD

API Governance Rules

Mews API Rules

34 rules · 5 errors 12 warnings 17 info

SPECTRAL

JSON Structure

Booking Engine Address Structure

0 properties

JSON STRUCTURE

Booking Engine Age Category Structure

0 properties

JSON STRUCTURE

Booking Engine Availability Block Structure

0 properties

JSON STRUCTURE

Booking Engine Country Structure

0 properties

JSON STRUCTURE

Booking Engine Currency Structure

0 properties

JSON STRUCTURE

Booking Engine Customer Structure

0 properties

JSON STRUCTURE

Booking Engine Enterprise Structure

0 properties

JSON STRUCTURE

Booking Engine Exchange Rate Structure

0 properties

JSON STRUCTURE

Booking Engine Language Structure

0 properties

JSON STRUCTURE

Booking Engine Payment Request Structure

0 properties

JSON STRUCTURE

Booking Engine Payment Structure

0 properties

JSON STRUCTURE

Booking Engine Product Structure

0 properties

JSON STRUCTURE

Booking Engine Rate Group Structure

0 properties

JSON STRUCTURE

Booking Engine Rate Structure

0 properties

JSON STRUCTURE

Booking Engine Reservation Group Structure

0 properties

JSON STRUCTURE

Booking Engine Reservation Structure

0 properties

JSON STRUCTURE

Booking Engine Restriction Structure

0 properties

JSON STRUCTURE

Booking Engine Service Structure

0 properties

JSON STRUCTURE

Connector Billing Accounting Item Structure

0 properties

JSON STRUCTURE

Connector Billing Bill Structure

0 properties

JSON STRUCTURE

Connector Billing Counter Structure

0 properties

JSON STRUCTURE

Connector Billing Ledger Balance Structure

0 properties

JSON STRUCTURE

Connector Billing Order Item Structure

0 properties

JSON STRUCTURE

Connector Billing Tax Environment Structure

0 properties

JSON STRUCTURE

Connector Billing Taxation Structure

0 properties

JSON STRUCTURE

Connector Configuration Department Structure

0 properties

JSON STRUCTURE

Connector Customers Companionship Structure

0 properties

JSON STRUCTURE

Connector Customers Company Structure

0 properties

JSON STRUCTURE

Connector Customers Loyalty Program Structure

0 properties

JSON STRUCTURE

Connector Customers Loyalty Tier Structure

0 properties

JSON STRUCTURE

Connector Operations Account Note Structure

0 properties

JSON STRUCTURE

Connector Operations Account Structure

0 properties

JSON STRUCTURE

Connector Operations Device Structure

0 properties

JSON STRUCTURE

Connector Operations Message Structure

0 properties

JSON STRUCTURE

Connector Operations Message Thread Structure

0 properties

JSON STRUCTURE

Connector Operations Task Structure

0 properties

JSON STRUCTURE

Connector Payments Cashier Structure

0 properties

JSON STRUCTURE

Connector Payments Credit Card Structure

0 properties

JSON STRUCTURE

Connector Payments Preauthorization Structure

0 properties

JSON STRUCTURE

Connector Pos Outlet Bill Structure

0 properties

JSON STRUCTURE

Connector Pos Outlet Item Structure

0 properties

JSON STRUCTURE

Connector Pos Outlet Structure

0 properties

JSON STRUCTURE

Connector Reservations Resource Structure

0 properties

JSON STRUCTURE

Connector Reservations Routing Rule Structure

0 properties

JSON STRUCTURE

Connector Reservations Source Structure

0 properties

JSON STRUCTURE

Connector Resources Resource Block Structure

0 properties

JSON STRUCTURE

Connector Services Product Category Structure

0 properties

JSON STRUCTURE

Connector Services Voucher Code Structure

0 properties

JSON STRUCTURE

Connector Services Voucher Structure

0 properties

JSON STRUCTURE

Example Payloads

Resources

🔗
Website
Website
🌐
Portal
Portal
🔗
Documentation
Documentation
🚀
GettingStarted
GettingStarted
🔗
APIReference
APIReference
🔑
Authentication
Authentication
👥
GitHubOrganization
GitHubOrganization
👥
Mews Open API documentation source
GitHubRepository
👥
.NET fiscalization library for government e-invoice reporting
GitHubRepository
👥
Flutter and Dart open-source packages maintained by Mews
GitHubRepository
👥
Mews engineering blog and developer microsite source
GitHubRepository
📰
Mews Engineering and R&D Blog
Blog
📰
Mews Hospitality Blog
Blog
🟢
StatusPage
StatusPage
📝
Become a Mews Partner
Signup
💰
Pricing
Pricing
📜
TermsOfService
TermsOfService
📜
PrivacyPolicy
PrivacyPolicy
💬
Support
Support
💬
Partner Success email
Support
🔗
About
About
🔗
Careers
Careers
🔗
Mews Marketplace - 1,000+ hospitality integrations
Marketplace
🔗
LinkedIn
LinkedIn
📦
Flutter / Dart Open-Source Packages
SDKs
📦
.NET Fiscalizations Library (Government E-Invoice Reporting)
SDKs
📦
FuncSharp - Functional Programming in C#
SDKs
🔧
Awesome Mews - Curated Engineering Resources
Tools
💻
Mews Open API Documentation Source
CodeExamples
🔗
Rules
Rules
🔗
Vocabulary
Vocabulary
🔗
Plans
Plans
🔗
RateLimits
RateLimits
🔗
FinOps
FinOps

Sources

Raw ↑
opencollection: 1.0.0
info:
  name: Mews Connector API — Services and Products
  version: v1
request:
  auth:
    type: apikey
    key: ClientToken
    value: '{{ClientToken}}'
    placement: header
items:
- info:
    name: Product categories
    type: folder
  items:
  - info:
      name: Mews Get All Product Categories
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/productCategories/getAll
      body:
        type: json
        data: '{}'
    docs: Returns all categories of products. Note this operation uses [Pagination](https://mews-systems.gitbook.io/connector-api/guidelines/pagination/)
      and supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property).
- info:
    name: Product service orders
    type: folder
  items:
  - info:
      name: Mews Get All Product Service Orders
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/productServiceOrders/getAll
      body:
        type: json
        data: '{}'
    docs: Returns all product service orders associated with the given enterprise. This operation uses [Pagination](https://mews-systems.gitbook.io/connector-api/guidelines/pagination/)
      and supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property/).
- info:
    name: Products
    type: folder
  items:
  - info:
      name: Mews Get Product Pricing
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/products/getPricing
      body:
        type: json
        data: '{}'
    docs: 'Returns prices for a given product for a specified time interval. UTC timestamps must correspond to the start boundary
      of a time unit, e.g. 00:00 converted to UTC for a time unit of "Day". Other timestamps are not permitted. The __maximum
      size of time interval__ depends on the service''s time unit: 100 hours if hours, 100 days if days, or 24 months if months.
      For more information about time units, see [Time unit](https://mews-systems.gitbook.io/connector-api/concepts/time-units).
      This operation s'
  - info:
      name: Mews Update Product Pricing
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/products/updatePrice
      body:
        type: json
        data: '{}'
    docs: Updates the prices for a given product. You can make multiple price updates with one API call, and for each one
      specify the price amount per [Time unit](https://mews-systems.gitbook.io/connector-api/concepts/time-units) and the
      time interval for which it applies. The price will be updated for all service time units that the specified time interval
      intersects. It is not permitted to update historical prices older than specified by `EditableHistoryInterval`. This
      operation supports [Portfolio Acce
  - info:
      name: Mews Get All Products
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/products/getAll
      body:
        type: json
        data: '{}'
    docs: Returns all products offered together with the specified services. Note this operation uses [Pagination](https://mews-systems.gitbook.io/connector-api/guidelines/pagination/)
      and supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property/).
  - info:
      name: Mews Delete Products
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/products/delete
      body:
        type: json
        data: '{}'
    docs: Deletes specified products. This operation supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property/).
- info:
    name: Service order notes
    type: folder
  items:
  - info:
      name: Mews Add Service Order Notes
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/serviceOrderNotes/add
      body:
        type: json
        data: '{}'
    docs: Adds one or more notes with a provided text to a specific service order. Service orders can be reservations or product
      orders.
  - info:
      name: Mews Update Service Order Notes
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/serviceOrderNotes/update
      body:
        type: json
        data: '{}'
    docs: Updates one or more given service order notes with new text.
  - info:
      name: Mews Get All Service Order Notes
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/serviceOrderNotes/getAll
      body:
        type: json
        data: '{}'
    docs: "Returns all notes associated with the given service orders. Service orders can be reservations or product orders.\
      \ Note this operation uses [Pagination](../guidelines/pagination.md) and supports [Portfolio Access Tokens](../guidelines/multi-property.md).\r\
      \n> **Service order:** This is the general name for an order made against a service, which includes both 'stay' service\
      \ orders, called [Reservations](reservations.md#reservation), and 'product' service orders, which we simply call [Orders](orders."
  - info:
      name: Mews Delete Service Order Notes
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/serviceOrderNotes/delete
      body:
        type: json
        data: '{}'
    docs: Deletes service order notes.
- info:
    name: Service overbooking limits
    type: folder
  items:
  - info:
      name: Mews Get All Service Overbooking Limits
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/serviceOverbookingLimits/getAll
      body:
        type: json
        data: '{}'
    docs: Returns all service overbooking limits. Note this operation uses [Pagination](https://mews-systems.gitbook.io/connector-api/guidelines/pagination/)
      and supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property/).
  - info:
      name: Mews Set Service Overbooking Limits
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/serviceOverbookingLimits/set
      body:
        type: json
        data: '{}'
    docs: Adds new service overbooking limits with the specified conditions. Past overbooking limits cannot be updated outside
      of `OperationalEditableHistoryInterval`. Care is needed to specify `FirstTimeUnitStartUtc` and `LastTimeUnitStartUtc`
      in the correct format - see [Datetimes](https://mews-systems.gitbook.io/connector-api/guidelines/serialization#datetimes).
      This operation supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property/).
  - info:
      name: Mews Clear Service Overbooking Limits
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/serviceOverbookingLimits/clear
      body:
        type: json
        data: '{}'
    docs: Deletes service overbooking limits that exactly match the specified conditions. This operation is intended to be
      used alongside `serviceOverbookingLimits/set`. The specified conditions must be met exactly. The time interval, however,
      does not need to correspond to an existing service overbooking limit in the system, instead the API uses a splicing
      algorithm to work out how to divide up any existing service overbooking limit to meet the specified time interval. Past
      overbooking limits cannot be c
- info:
    name: Services
    type: folder
  items:
  - info:
      name: Mews Get All Services
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/services/getAll
      body:
        type: json
        data: '{}'
    docs: 'Returns all services offered by the enterprise.

      Note this operation uses [Pagination](https://mews-systems.gitbook.io/connector-api/guidelines/pagination/) and supports
      [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property).'
  - info:
      name: Mews Update Service Availability
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/services/updateAvailability
      body:
        type: json
        data: '{}'
    docs: Updates the number of available resources in [Resource category](https://mews-systems.gitbook.io/connector-api/operations/resources/#resource-category)
      by a certain amount (relative adjustment). Note that availabilities are defined per time unit, so when the server receives
      the UTC interval, it first converts it to enterprise timezone and updates the availability on all time units that the
      interval intersects. It's not allowed to update past availabilities outside of `EditableHistoryInterval`, f
  - info:
      name: Mews Get Service Availability
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/services/getAvailability
      body:
        type: json
        data: '{}'
    docs: Returns availability of a bookable service for a specified time interval including applied availability adjustments.
      Availability will be returned for all service time units that the specified time interval intersects. So, for example,
      an interval `1st Jan 23:00 UTC - 1st Jan 23:00 UTC` will result in one price for `2nd Jan`, while Interval `1st Jan
      23:00 UTC - 2nd Jan 23:00 UTC` will result in two prices for `2nd Jan` and `3rd Jan` (assuming a time unit period of
      "Day"). UTC timestamps must cor
  - info:
      name: Mews Get Service Availability (ver 2024-01-22)
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/services/getAvailability/2024-01-22
      body:
        type: json
        data: '{}'
    docs: 'Returns selected availability and occupancy metrics of a bookable service for a specified time interval, similar
      to [the availability & occupancy report](https://help.mews.com/s/article/Availability-Occupancy-report). Availability
      will be returned for all service time units that the specified time interval intersects. So, for example, an interval
      `1st Jan 23:00 UTC - 1st Jan 23:00 UTC` will result in one time unit for `2nd Jan`, while Interval `1st Jan 23:00 UTC
      - 2nd Jan 23:00 UTC` will result '
- info:
    name: Voucher codes
    type: folder
  items:
  - info:
      name: Mews Add Voucher Codes
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/voucherCodes/add
      body:
        type: json
        data: '{}'
    docs: Adds voucher codes to the specified [Vouchers](https://mews-systems.gitbook.io/connector-api/operations/vouchers/#voucher).
      Note this operation supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property).
  - info:
      name: Mews Delete Voucher Codes
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/voucherCodes/delete
      body:
        type: json
        data: '{}'
    docs: Delete specified voucher codes. Note this operation supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property).
  - info:
      name: Mews Get All Voucher Codes
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/voucherCodes/getAll
      body:
        type: json
        data: '{}'
    docs: Returns all voucher codes filtered by [Voucher](https://mews-systems.gitbook.io/connector-api/operations/vouchers/#voucher)
      or other filter parameters. Note this operation uses [Pagination](https://mews-systems.gitbook.io/connector-api/guidelines/pagination/)
      and supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property).
- info:
    name: Vouchers
    type: folder
  items:
  - info:
      name: Mews Get All Vouchers
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/vouchers/getAll
      body:
        type: json
        data: '{}'
    docs: Returns all rate vouchers filtered by [Service](https://mews-systems.gitbook.io/connector-api/operations/services/#service),
      voucher code or voucher identifier. Note this operation uses [Pagination](https://mews-systems.gitbook.io/connector-api/guidelines/pagination/)
      and supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property).
  - info:
      name: Mews Add Vouchers
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/vouchers/add
      body:
        type: json
        data: '{}'
    docs: Adds the specified vouchers to the specified [Services](https://mews-systems.gitbook.io/connector-api/operations/services/#service).
      Note this operation supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property).
  - info:
      name: Mews Update Vouchers
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/vouchers/update
      body:
        type: json
        data: '{}'
    docs: Updates information about the specified vouchers. Note this operation supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property).
  - info:
      name: Mews Delete Vouchers
      type: http
    http:
      method: POST
      url: https://api.mews.com/api/connector/v1/vouchers/delete
      body:
        type: json
        data: '{}'
    docs: Delete specified vouchers. Note this operation supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property).
bundled: true