The Metadata Push APIs enable Hotel Trader to transmit metadata updates for hotels, roomtypes, rateplans, cancellation policies, and taxes. These APIs are designed so the client system can receive and process metadata updates seamlessly.
Key Features and Processing Order
Separate Messages for Metadata Types
There are distinct messages for each type of metadata:
Sequential Processing
Metadata messages for a given property must be processed in the order they are received.
Hotel Trader ensures that a message is sent only after the previous one has been successfully processed.
Non-Incremental Updates
Metadata updates are not incremental. Each metadata push contains all fields of the relevant object, not just the updated fields.
Example: If a new bedtype is added to an existing hotel, the entire Hotel Metadata Request Object, including all bedtypes, taxes, amenities, and currencies, will be sent to the client.
Error Handling and Response Expectations
Basic Validations And Asynchronous Processing.
The client validates all mandatory fields in the metadata request. If any validation errors occur, the client must respond with the appropriate error codes; otherwise, it should return a success response. After sending a valid response, the client should process the object asynchronously.
Failure Scenarios for Retries
Hotel Trader retries metadata push messages when any of the following failures occur:
- The client drops the connection without returning a response.
- A connection timeout occurs.
- The connection is refused by the client.
- An SSL handshake error occurs.
Retry Mechanism
Retries follow Hotel Trader’s predefined internal schedules.