Enterprise Guidelines
High-volume channel partners, PMS vendors, and enterprise integrations should follow these architectural standards to ensure maximum performance, fault tolerance, and seamless synchronization with Google Hotel Centre.
1. Idempotency & EchoToken#
Every rate or availability request supports the EchoToken attribute on the root XML node (e.g. EchoToken="TRX_987654321" ). We strongly recommend generating a unique UUID or transaction identifier for each push. If a network timeout or HTTP connection drop occurs, resending the identical payload with the same EchoToken allows safe retries.
2. Delta / incremental pushes#
To reduce network overhead and ensure low-latency processing, push delta updates (changes in rates, restrictions, or inventory for affected date windows) rather than full 365-day property re-downloads whenever possible. Full refreshes should only be executed during initial onboarding or periodic reconciliation audits.
3. Batching & payload limits#
Combine multiple room configurations and rate plan updates into a single XML request message. A single OTA_HotelRateAmountNotifRQ or OTA_HotelAvailNotifRQ request can contain up to 100 message blocks per transaction. Payload sizes are capped at 2MB per request.
4. Timezone & date standard#
All dates ( Start and End attributes) must follow the standard ISO-8601 format YYYY-MM-DD (e.g. 2026-08-20 ). Date ranges are inclusive of the start date and end date. Ensure date ranges align with the property's local check-in timezone.