Understanding the Hotel Trader Push API Components
1. Metadata Push and Audit APIs (Mandatory)
All clients must implement these APIs to automate the metadata creation and update process
- Metadata Push API (REST API): Sends metadata such as hotel details, rate plans, room types, cancellation policies, and taxes.
- Metadata Audit API(REST API): Audits the metadata received and processed by the client’s system.
2. Receiving Availability, Rates, and Inventory (Mandatory)
Push clients must implement the PUSH XML schema to receive:
- Availability and inventory (OTA_HotelAvailNotifRQ, OTA_HotelAvailNotifRS)
- Rates (OTA_HotelRatePlanNotifRQ)
3. Price Check
Perform price checks using the GraphQL Quote method before making a reservation to ensure accurate rates and availability.
We strongly recommend integrating and using the Price Check API even though it is not mandatory.
4. Pushing Reservations
Send reservations upstream and get confirmation which includes the CRS/PMS confirmation codes.
Integration Path
Quick overview of the integration path:
- REST based Content API: Receive and keep your metadata updated in real-time.
- SOAP XML Schema: Receive ARI from Hotel Trader through a push integration
- OTA_HotelAvailNotifRQ: Receive availability objects.
- OTA_HotelRatePlanNotifRQ: Receive rates and inventory.
- GraphQL Price Check API (Quote - Hybrid): Checks the latest price before sending reservations.
- GraphQL Reservations APIs:
- Sends reservation requests.
- Modify and cancel reservations.
- Retrieves existing reservations.
Existing clients can continue to use the OTA_HotelResNotifRQ and OTA_HotelReadResRQ objects to send and retrieve reservations using the XML based schema.