The Mews APIs
Last updated
Was this helpful?
Last updated
Was this helpful?
Mews currently supports three separate APIs, each serving a different purpose.
Three individual APIs
The documentation for each API is self-contained and consists of two parts:
A set of guidelines on how to use the API
A detailed reference for all the API operations
And each API is hosted as a public GitHub repository.
This API is a general-purpose API that gives access to data and services in Mews Operations. The API supports many use cases, including Kiosk, Point Of Sale, Reservations Data, Upselling and Events Management, to name just a few. We encourage you to explore the API and innovate new solutions for our customers!
For the full documentation, see
This API is for Channel Managers and other distribution channels to fetch availability, rates and inventory data, and make reservations.
For the full documentation, see
This API is for booking engines to enable guests to create reservations directly in Mews. Please note that for custom booking engine solutions, connected properties will need a Mews Enterprise subscription.
For the full documentation, see
Important: The Mews Booking Engine API is designed to be consumed directly by front-end clients. It is unsuitable for continuous polling by a single server due to its built-in anti-scraping protection and such requests can fail. For server to server communication, please refer to the .
If you are a Channel Manager, or a bulk sales or distribution channel such as an Online Travel Agent, then you will want the . If you are implementing a Booking Engine for your customers to book with you directly, you will want the . For all other use cases, use the . Please also take a look at , where you can find more information on individual use cases and links to more details in the documentation for the appropriate API.