Booking Engine Guide
  • Mews Booking Engine Guide
  • Booking Engine Standalone
    • Getting started
    • Deeplinks
  • Booking Engine Widget
    • Getting started
    • Use cases
      • Prerequisites
      • Testing in the Demo environment
      • Using your own Date inputs
      • Multiple enterprises and pre-selected locations
      • Disabling widget caching
    • Advanced guide
    • Reference
    • Troubleshooting
  • Booking Engine API
    • Usage guidelines
      • Authentication
      • Requests
      • Responses
      • Environments
      • Images
      • Supported currency codes
      • Supported language codes
    • Use cases
      • Availability blocks
      • On session payments
      • Payment card authorization
      • Supporting payment cards
    • API Operations
      • Availability blocks
      • Configuration
      • Hotels
      • Payment cards
      • Reservations
      • Reservation groups
      • Services
      • Vouchers
    • Deprecations
  • Integrations
    • Google Tag Manager
    • Google Triggers Reference
    • Google Tag Manager Configuration
    • Google Analytics cross-domain tracking
  • FAQ
    • Ways to integrate
    • Migration off the mews.li domain
  • Changelog
    • Changelog 2024
    • Changelog 2023
    • Changelog 2022
    • Changelog 2021
    • Changelog 2020
Powered by GitBook
On this page
  • Client authentication
  • Registration
  • Environments
  • Sample client name
  • Client authorization

Was this helpful?

  1. Booking Engine API
  2. Usage guidelines

Authentication

PreviousUsage guidelinesNextRequests

Last updated 2 months ago

Was this helpful?

The Mews Booking Engine API is a public API that requires client authentication and authorization.

Client authentication

Authentication is the process of verifying the identity of the client. To access the API, you must identify your client application by providing the Client property in all requests. This ensures that your client application is recognized and allowed to interact with the API.

Registration

Your client application needs to be pre-registered with Mews Support. You can open a ticket from Mews Operations via the . The registration request should contain:

  • Client - the name of the client application that will be used for every API request

  • Email - an email contact for your development department; this email will be used by our developers to notify you about any breaking changes in the API

  • Environment - the name of the environment you are accessing, either Production or Demo.

Environments

We offer two environments, Production and Demo. Use Demo during API implementation, and Production only for live customer sites. The two environments have separate client lists, so make sure you are registered in Production before you move your implementation to the Production environment. For details, see our page.

Sample client name

Before the registration of your Client name is confirmed, you can use the sample client name below. This client name will only work in the Demo environment. Keep in mind that this must be replaced by your proper Client name as soon as you finish the registration process.

{
    "Client": "My Client 1.0.0"
}

Client authorization

Authorization is the process of determining what the authenticated client is allowed to do. In this case, it is sufficient to know the unique identifier of a hotel or other enterprise in order to access it. However, the client must be authenticated by providing the Client property in all requests to ensure it has the necessary permissions to interact with the API.

Mews Digital Assistant
Environments