Channel Manager API
  • Mews Channel Manager API
  • Usage guidelines
    • Authentication
    • Requests
    • Responses
    • Environments
    • Compliance
  • Concepts
    • Restrictions
  • Use cases
    • Channels
    • Inventory updates
  • API Operations (Mews)
    • Configuration
    • Availability blocks
    • Inventory
    • Reservations
  • API Operations (CHM)
    • Availability blocks
    • Inventory
    • Reservations
    • Notifications
  • Your integration journey
    • Certification
    • Certification tests
  • Deprecations
  • Changelog
    • Changelog 2023
    • Changelog 2022
    • Changelog 2021
    • Changelog 2020
    • Changelog 2019
    • Changelog 2018
    • Changelog 2017
Powered by GitBook
On this page
  • Mews side
  • Channel Manager side
  • Providing endpoints to Mews

Was this helpful?

  1. Usage guidelines

Requests

PreviousAuthenticationNextResponses

Last updated 4 months ago

Was this helpful?

Both sides of the API accept only HTTPS POST requests with Content-Type set to application/json and with JSON body content depending on the operation to be performed.

Mews side

All Mews API operations follow this address pattern, with the exception of :

[PlatformAddress]/api/channelManager/v1/[Operation]
  • PlatformAddress - the base address of the Mews platform, which depends on the environment (e.g. test, demo, production)

  • Operation - the name of the API operation

For each environment, the clientToken will be provided to you by Mews. For development purposes, use the .

Transport Layer Security: For security reasons, Mews API endpoints support TLS security protocol version 1.2 or higher.

Channel Manager side

All Channel Manager API operations are expected to follow this address pattern:

[PlatformAddress]/[Operation]
  • PlatformAddress - the base address of the Channel Manager side of the API

  • Operation - the name of the API operation

Providing endpoints to Mews

Please provide Mews with endpoint URLs for the following API operations once they are deployed. Mews needs them for both the Test environment and the Production environment to be able to send data. Mews doesn't require all endpoint URLs to be provided at once. We recommend having a different [PlatformAddress] for each environment to prevent test data and live data from getting mixed up. For the same reason, clientToken should differ between each environment.

Required:

Optional:

Change notification
Test environment
Confirm booking
Update prices
Update availability
Update restrictions
Mews: Process group