Request Formats & Validations
Hotel Trader uses JSON formats for requests & responses.
If a request to the Booking Service contains any missing data for required attributes, Hotel Trader APIs will return an error indicating incorrect/invalid values. For example, zero rates/taxes for any stay date, past check-in date, etc.
For more information see the Error Codes page.
Validation checks are performed by Hotel Trader for various restrictions against property rate plans. For example minLOS, maxLOS, minLeadTime, day rate checks like isOpen, isOpenToDeparture, isOpenToArrival, Room, and RatePlan active status. These validation checks differ based on request type - whether it is a new booking or a modification of a certain type. The response from Hotel Trader will include the cheapest available rates based on the parameters provided in the request.
Authorization Mechanism (Credentials)
We use base-64 encoded username/password-based authorization over HTTPS to provide access to the API. Hotel Trader will provide the encoded token in advance of the commencement of integration for each environment.
Expected HTTP Headers
Our API is designed to work with Content-Type application/JSON, so the client needs to send the following headers with each GET or POST request:
| Attribute Name | Description |
|---|---|
| Content-Type | application/JSON |
| Authorization | This is the authorization token provided by Hotel Trader that needs to be included in each request header. |
All travel agencies are expected to make live search requests via the Hotel Trader GraphQL API. If you want to cache Hotel Trader rates in advance of a user search please ask a Hotel Trader team member for additional support information. Please note that caching behavior without pre-approval may result in connectivity being disabled.