Developer Docs
  • Our Products
    • Channel Manager
      • Integration and Onboarding Flow
      • 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
      • Onboarding process
      • Certification - Demand
      • 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
    • Integration Process
    • Certification - Demand
    • 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
  • UltraDirect
    • Integration Process
    • Certification
    • Ultradirect transaction sets - XML
      • Transaction header formats
      • Booking transactions
        • Booking request message format..
        • Request message format - Cancel
        • Request message format - Commit/Rollback
        • Request message format - Modify
        • Response message format - Booking
      • Enhanced shopping (EST)
        • Requesting Specific Rates
        • Request message format
        • Response message format.
      • Rate and availability transactions
        • Standard multi-availability
          • Request & Response message format
      • Rate Rules
        • Request message format
        • Response message format
      • Reference data transactions
        • Request message format..
        • Response message format..
      • Single property availability
        • Request message format
        • Response message format
    • XML ultradirect specifications
      • Overview
        • Transaction list
      • Interface requirements
      • Transaction meta data
    • Error Codes..
    • UltraDirect Transaction Samples and Usage
      • Using UltraDirect (Seamless, a real-time transaction)
      • EST (Enhanced Shopping Transaction)
      • Rate Rules
      • Book Reservation
      • Cancellation
      • Book Reservation with session control
      • Modification
      • Booking Storage and Retrieval
      • List of Test Credit Cards
      • Test properties in UAT
      • Guarantee Type and Method Combinations
    • xml ultradirect codes
  • Get in Touch
    • Questions?
Powered by GitBook
On this page
  • 🧾 Step 1: Commercial Arrangements
  • πŸ“ž Step 2: Tri-Party Kick-off Call
  • βš™οΈ Step 3: Configuration Setup
  • πŸ’» Step 4: API Development
  • βœ… Step 5: Certification
  • πŸš€ Step 6: Roll Out
  1. UltraDirect

Integration Process

This document outlines the end-to-end process for integrating a Demand Partner with RateGain and Hotel Suppliers. It includes all necessary steps, ownership, and milestones from commercial setup to full rollout.


🧾 Step 1: Commercial Arrangements

  • A commercial agreement must be signed between the Demand Partner & RateGain.

  • A separate commercial agreement is required between the Demand Partner & Hotel Supplier.

  • Approval from RateGain’s commercial team is mandatory before initiating integration.


πŸ“ž Step 2: Tri-Party Kick-off Call

  • A Tri-Party Kick-Off Call is conducted between RateGain, the Demand Partner, and the Hotel Supplier.

  • Objectives of the call:

    • Review the Kick-Off Questionnaire to clarify tasks, ownership, and next steps.

    • Understand expected timelines from the demand partner for setup, development, testing, and certification.

    • Highlight exceptions (if any).

    • Create the Statement of Work (SOW) pre-Kick-off call.

    • Define and agree on integration quality metrics for the Pilot and Go-Live phases.


βš™οΈ Step 3: Configuration Setup

  • Company profile creation

  • IP whitelisting

  • Generation of SGA (Source Code)

  • VIP URL creation for:

    • Availability

    • Booking

  • Portal self-registration (documentation provided separately)

  • SFTP setup

  • Nightly ODDCCN enablement

  • Creation of NRCs (Negotiated Rate Codes)

  • Portal access for PDS (Property Download Site)


πŸ’» Step 4: API Development

  • SOW sign-off by Demand Partner (prepared by RateGain)

  • API walkthrough for:

    • ARI (Availability, Rates, Inventory)

    • Static Content (if applicable)

  • RateGain to provide:

    • API documentation

    • Sample XMLs

    • Ongoing technical support

  • A project plan is created and tracked by RateGain based on committed timelines.

  • Regular weekly/bi-weekly sync-up calls for:

    • Status tracking

    • Query/blocker resolution


βœ… Step 5: Certification

  • Certification to be conducted in UAT or Production

  • Quality Check:

    • Verify data consumption by the Demand Partner

    • Ensure the correct display of mandatory content on the Demand Partner’s platform

  • Run a pilot with a limited number of properties

  • Upon successful results β†’ Go Live


πŸš€ Step 6: Roll Out

  • Pilot launch with a limited set of properties

  • Execute a scheduled rollout plan for upcoming batches

  • Complete final rollout for all properties under contract


PreviousUltraDirectNextCertification

Last updated 21 days ago