Mews

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 engines that create reservations directly in Mews. It is designed for front-end client consumption rather than server-to-server use, exposes enterprise configuration, availability, rate plans, products, vouchers and reservation creation, and is the foundation behind Mews-built and partner-built booking flows including widgets, kiosks, and direct-booking websites.

Mews Booking Engine API is one of 5 APIs that Mews publishes on the APIs.io network.

Tagged areas include Booking Engine, Reservations, Distribution, Direct Booking, and Guest. The published artifact set on APIs.io includes API documentation, an API reference, and a changelog.

GitHub

Documentation

📖
Documentation
https://docs.mews.com/booking-engine-guide
📖
Documentation
https://docs.mews.com/booking-engine-guide/guidelines
📖
APIReference
https://docs.mews.com/booking-engine-guide/operations

Other Resources

🔗
ChangeLog
https://docs.mews.com/booking-engine-guide/changelog

API entry from apis.yml

apis.yml Raw ↑ 
aid: mews-systems:mews-booking-engine-api
name: Mews Booking Engine API
tags:
- Booking Engine
- Reservations
- Distribution
- Direct Booking
- Guest
humanURL: https://docs.mews.com/booking-engine-guide
baseURL: https://api.mews.com/api/distributor/v1
properties:
- url: https://docs.mews.com/booking-engine-guide
  type: Documentation
- url: https://docs.mews.com/booking-engine-guide/guidelines
  type: Documentation
- url: https://docs.mews.com/booking-engine-guide/operations
  type: APIReference
- url: https://docs.mews.com/booking-engine-guide/changelog
  type: ChangeLog
description: 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 engines that create
  reservations directly in Mews. It is designed for front-end client consumption rather than server-to-server
  use, exposes enterprise configuration, availability, rate plans, products, vouchers and reservation
  creation, and is the foundation behind Mews-built and partner-built booking flows including widgets,
  kiosks, and direct-booking websites.