Processing ARI and Metadata Messages
Clients integrating with Hotel Trader through the Push Model are required to implement both the Push API (for ARI messages) and the Content API (for metadata messages). Your systems must be optimized for quick and reliable responses to avoid timeouts, processing delays, or synchronization issues.
Response Time Expectations
- Timeout Policy: Hotel Trader will timeout any push message (ARI or metadata) if no response is received within 15 seconds.
- Recommended Response Time: Your endpoint is expected to respond within 2 seconds.
- Background Processing: If processing takes longer than 2 seconds:
- Validate the mandatory fields in the request.
- Respond with a Success status immediately to acknowledge receipt.
- Continue background processing without delaying the response.
Getting Your Servers Ready
High Data Volumes and Concurrency Considerations
Hotel Trader’s systems push large amounts of data, particularly when a new hotel is enabled or disabled. Your system must be prepared for:
- ARI Messages:
- One ARI message may contain 700+ days of availability, rates, and inventory.
- Up to 10 concurrent ARI messages may be sent to your server.
- If 10 messages are in progress, an 11th message is queued until a response is received for one of the prior messages.
- Metadata Messages:
- Each hotel launch can involve 100-200 metadata messages, covering properties, rateplans, room types, taxes, and cancellation policies.
- Batches of up to 1,000 properties may be launched at once.
- Metadata transmission for a batch may take 5-10 minutes to complete within Hotel Trader’s system.
Key Considerations for Clients
To ensure smooth integration and avoid bottlenecks, your systems must support:
- Concurrent Processing: Handle simultaneous data transmissions efficiently.
- Scalability: Dynamically scale infrastructure to handle high-volume bursts.
- Efficient Data Pipelines: Optimize data ingestion, validation, and storage processes to prevent processing delays.
- Performance Testing: Rigorously test your production environment to ensure it can handle increasing message loads as more properties are added.
Messaging Format
Hotel Trader follows a customized OTA XML (HTNG2008a) specification for Demand Client integration. Modifications are made to align with upstream integrations with various Central Reservation Systems (CRSs). Developers integrating with Hotel Trader must be familiar with HTNG2008a specifications and end-to-end hotel PUSH ARI and metadata processing.
Transport Protocol Specifications
- HTTPS
- Public IP address to whitelist for ARI messages NAT IP Address:
- 44.214.248.55
- 52.55.205.152
- 107.20.164.116
- Public IP address for reservation messages - HAProxy IP Address [To be provided if required by Client system]
- Protocols enabled
- TLS1.2
- Protocols NOT enabled
- SSLv3
- SSLv2
- TLS1.1
- TLS1.0
- Cipher suites enabled
- TLS_RSA_WITH_AES_128_CBC_SHA (0x002F)
- TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
- TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003C)
- TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003D)
- TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009C)
- TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009D)
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xC013)
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xC014)
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xC027)
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xC028)
- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xC02F)
- TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xC030)
- SNI is disabled