Developer Docs
  • Our Products
    • RG Bridge - Supply (Push)
      • Integration Overview
        • Vision of Integration
          • Commercial value and business case
        • Information Data flow
          • One way integration
          • Two Way integration – ARI Broadcast and Reservation fetch
          • Information delivery mechanism
        • Technical feasibility of integration
          • Test property setup
          • Sample reservation data
        • RG Bridge Setup
        • Contract
        • Project Plan
        • Certification
        • Monitoring and after sales support
        • Integration checklist
      • Interface Specifications – Availability and Rates Notification Service
        • RG Bridge Integration Process
        • Intended Audience
        • Typographical Conventions
        • Technical Overview
        • Operations
          • Availability Notification
            • OTA_HotelAvailNotifRQ
              • Change in Inventory count
              • Change in availability status and Restrictions
            • OTA_HotelAvailNotifRS
            • XML Usage Specification
          • Rate Change Notification
            • OTA_HotelRateAmountNotifRQ
            • XML Usage Description
            • OTA_HotelRateAmountNotifRS
            • XML Usage Specification
          • Points to remember
      • Interface Specifications – Reservation Notification Service
        • RG Bridge integration process
        • Intended audience
        • Typographical conventions
        • Technical overview
        • Operations
          • Reservation Notification
            • OTA_HotelResNotifRQ
            • XML Usage specification
            • Sample Reservation Messages
            • OTA_HotelResNotifRS
            • XML Usage specification
        • Points to remember
        • Code Lists
    • RG Bridge - Reservation Retrieval (Pull)
      • Technical overview
      • Operations
        • Reservation Retrieval
          • OTA_ReadRQ
          • XML Usage specification
          • OTA_ResRetrieveRS
          • XML Usage specification
        • Reservation Confirmation
          • OTA_NotifReportRQ
          • XML Usage specification
          • OTA_NotifReportRS
          • XML Usage specification
      • Code Lists
    • Direct Connect - Demand (Push)
      • Introduction
      • Interface Specifications – ARI Service
        • Technical Overview
        • Operation: Property List
          • HotelPropertyListGetRQ
          • HotelPropertyListGetRS
          • Test Use Cases
          • FAQ
        • Operation: Product List
          • HotelProductListGetRQ
          • HotelProductListGetRS
          • Test Use Cases
          • FAQ
        • Operation: ARI Get
          • HotelARIGetRQ
          • HotelARIGetRS
          • Test Use Cases
          • FAQ
        • Operation: ARI Update
          • HotelARIUpdateRQ
          • HotelARIUpdateRS
          • Test Use Cases
          • FAQ
        • Points to remember
        • Code Lists
      • Interface Specifications – Reservation Notification Service
        • Technical overview
          • Communication protocols
          • General design
          • Authentication
        • Operation: Reservation
          • OTA_HotelResNotifRQ
          • OTA_HotelResNotifRS
          • Test use cases
          • FAQ
    • Smart Distribution
      • Authentication Method
      • Book and Cancel Reservation
        • Transaction Header Formats
        • Book API
          • Book Reservation
          • Cancel Reservation
          • Booking Reservation Request Message Format
          • Booking Reservation Response Message Format
          • Cancel Reservation Request Message Format
      • Multiavailability (Enhanced Shopping Transaction)
        • Transaction Header Formats
        • Enhanced Shopping (EST) – Detailed Rate Information
          • Requesting Specific Rates
          • UltraDirect Account Author Negotiated Rate Processing
          • Unavailable Properties
          • UltraDirect Cache Processing
          • Enhanced Shopping Transaction Request Header Format
          • Enhanced Shopping Transaction Response Message Format
      • Pre-Book
        • Transaction Header Formats
        • Pre Book API
          • Pre-Book Request message format
          • Pre-Book Response message format
      • Property list and Booking Summary
        • PropertyList API
        • Booking Summary API
  • Content
    • Content Retrieve
      • SOAP/HTTP
        • SOAP Envelop
        • SOAP Body
        • Date and Time
        • Specifications for Currency Amounts
      • Transaction Specifications
      • Content Retrieval Request
      • Content Retrieval Response
    • Content Update
      • Overview
      • Transaction List
      • Transaction Flow
      • Batch processing
        • File naming convention
      • Multi-lingual capabilities
      • Associating media to textual content
      • Managing images
      • GDS content updates
      • Office of Foreign Assets Control (OFAC)
      • Interface requirements
        • SOAP envelope
        • Standard element formats
      • Transaction specifications
        • Data mapping of elements
        • Area Information
        • Affiliation information
        • Media information
        • Contact information
        • TPA extensions
        • GDS information
        • Response message
      • Codes lists
        • Credit Card
        • Error and Warning codes
        • Spoken Language
        • State and Country
      • Supported language codes
      • Client application generation using WSDL tool
  • Get in Touch
    • Questions?
Powered by GitBook
On this page
  1. Content
  2. Content Update

Transaction Flow

PreviousTransaction ListNextBatch processing

Last updated 24 days ago

A typical transaction flow to the HCD XML Update Interface consists of a request transaction, verification process, database update, and success or failure response.