Connector API
Search…
Guidelines
This section describes guidelines for general usage of the Mews Connector API and serves as a quick-start guide to kickstart your integration development.

Terminology

Some of the terms used in the API, such as enterprise, customer or resource may not be familiar. For example, we use resource to describe guest rooms and other types of bookable space. For a full description of all the terms used, see the Mews Glossary for Open API users.

Quick start

To begin with, Mews operates several environments. At the beginning of your development process, you'll be interested in the Demo environment. To get yourself familiar with the system and the types of data we provide, you can log in to Mews Operations using the email and password provided and check out the Mews system features.
Alternatively, you can start using the API right away, using the demo tokens below. Requests towards our API should be in JSON format and sent using POST method. Below is an example request which will return the configuration details for one of our test hotels. To begin with, Mews operates several environments. At the beginning of your development process, you'll be interested in the Demo environment. To get yourself familiar with the system and the types of data we provide, you can log in to Mews Operations using the email and password provided and check out the Mews system features.
Alternatively, you can start using the API right away, using the demo tokens below. Requests towards our API should be in JSON format and sent using POST method. Below is an example request which will return the configuration details for one of our test hotels. You can find out more about this API operation in Get configuration.
Endpoint URL:
https://api.mews-demo.com/api/connector/v1/configuration/get
Request payload:
1
{
2
"ClientToken": "E0D439EE522F44368DC78E1BFB03710C-D24FB11DBE31D4621C4817E028D9E1D",
3
"AccessToken": "7059D2C25BF64EA681ACAB3A00B859CC-D91BFF2B1E3047A3E0DEC1D57BE1382",
4
"Client": "NameOfYourCompanyOrApplication"
5
}
Copied!
If the response looks something like this, you've successfully made your first request!
1
{
2
"NowUtc": "2021-05-05T11:39:29Z",
3
"Enterprise": {
4
"Id": "c65ea6e9-2340-42f4-9136-ab3a00b6da22",
5
"ChainId": "8ddea57b-6a5c-4eec-8c4c-24467dce118e",
6
"CreatedUtc": "2020-01-06T11:05:44Z",
7
"Name": "Connector API Hotel (Net Pricing) TEST",
8
"TimeZoneIdentifier": "America/New_York",
9
"LegalEnvironmentCode": "US-DC",
10
"AccommodationEnvironmentCode": "US",
11
"AccountingEnvironmentCode": "DEFAULT",
12
"TaxEnvironmentCode": "US-DC",
13
"DefaultLanguageCode": "en-US",
14
"EditableHistoryInterval": "P0M2DT0H0M0S",
15
"WebsiteUrl": "https://www.mews.com/",
16
"Email": "[email protected]",
17
"Phone": "+12025555501xx",
18
"LogoImageId": "c90a8d7e-a332-45c0-ac44-ac5600a4116e",
19
"CoverImageId": "c867f682-4003-4518-b96c-abec0090a23b",
20
"Address": {},
21
"Currencies": [],
22
"Pricing": "Net",
23
"TaxPrecision": null
24
},
25
"PaymentCardStorage": {
26
"PublicKey": "1100016827"
27
}
28
}
Copied!
There are several serialization patterns that you should get familiar with in order to use the API correctly. For example, we work with times in UTC so you should be aware of the timezone the property is in (as can be seen on example above) as well as any daylight saving time changes, and adjust accordingly.
If you receive an error response, check the response codes and the message specified in response details to determine what went wrong. Note that if you encounter a 429 error with one of the testing demo credentials, it may be that multiple developers are using the same demo credentials and have exhausted our request limits. To minimize the impact this may have on your development efforts, we provide multiple sets of tokens for the test hotels that you can use in Demo.
Copy link
Contents
Quick start