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
  • Request body
  • Request limits

Was this helpful?

  1. Booking Engine API
  2. Usage guidelines

Requests

PreviousAuthenticationNextResponses

Last updated 3 months ago

Was this helpful?

The API accepts only HTTP POST requests with Content-Type set to application/json and JSON content dependent on the operation to be performed. All operations follow this address pattern:

[ApiBaseUrl]/api/distributor/v1/[Resource]/[Operation]
  • ApiBaseUrl

    • Base address of the Mews Booking Engine API, this depends on the (Demo or Production).

  • Resource

    • Logical group of operations, in most cases this identifies the target of the operation.

  • Operation

    • Name of the operation to be performed.

Request body

{
    "Client": "My Client 1.0.0",
    "LanguageCode": null,
    "CultureCode": null 
}
Property
Type
Contract
Description

Client

string

required

LanguageCode

string

optional

CultureCode

string

optional

  • All API operations require Client to be present in the request.

  • All API operations optionally accept LanguageCode and CultureCode. These can be used to enforce the language and culture of the operation, which affects for example the names of entities, descriptions or error messages. Both of these values must be defined together, otherwise default values for the enterprise are used.

Request limits

If you receive this error response, your system can re-try after an interval time, however some care is needed in choosing the interval time. In case of a 429 error, we include the Retry-After http header in the response to indicate how long you should wait before making a re-try attempt. Alternatively, you could implement something like an exponential backoff strategy, i.e. using a progressively longer wait between re-tries for consecutive error responses. Pausing for a fixed amount of time is never recommended. If you are receiving 429 Too Many Requests errors, then we would also recommend examining your implementation to see if it is possible to make design changes to reduce the load on our API and prevent the errors being generated in the first place.

Identification of the client, as described in .

Code of the language, see .

Code of the culture, see .

Mews implements API request limits in order to protect our systems against an excessive volume of calls which could compromise the service for all its users. The particular limits are dependent on circumstances. Regardless, your system should be prepared to receive a 429 Too Many Requests response in cases where you hit such a limit - see .

Environment
Responses
Authentication
Supported language codes
Supported language codes