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
  1. Our Products
  2. Channel Manager
  3. Direct Connect - Demand (Push)
  4. Interface Specifications – ARI Service

Points to remember

Partial Updates:

  • RG Channel Manager will always send partial updates to the channel.

    • Purpose: Allows a hotel to change any specific field (Allocation/ClosedOut/any restriction/Pricing type) for a day.

    • Validation: There should not be any validation at the channel end to expect any mandatory field in the update.

  • Allocation:

    • Manageable at Room level only by a channel partner.

    • Separate RQ for Allocation updates; other fields will be updated in another RQ.

  • Price:

    • Channel Manager will reject any updates with price=0; this should not be supported for any channel partner.

  • MinLOS and MaxLOS Rule:

    • MinLOS (Minimum Length of Stay) should always be lesser than or equal to MaxLOS (Maximum Length of Stay).

    • If MinLOS=4 and the current MaxLOS is 3 for the same product, the channel should fail the request with an error message.

  • Monthly Data Updates:

    • Channel partners should accept an update with 1 month of data in a single RQ.

    • If there are 20 days updated for a month, RezGain will send 1 update RQ with all 20 days included.

  • Invalid Test Scenarios:

    • Invalid credentials/HotelCode/RoomCode/RateCode cannot be tested through the sandbox; this will be validated during the certification process.

    • Only 14 days of updates can be tested through the sandbox tool.

  • Cross-Month Updates:

    • Allows a hotel to update multiple dates across the month, e.g., 25 Jan-3 Feb in a single update RQ.

  • Cross-Year Updates:

    • Allows a hotel to update multiple dates across the year, e.g., 25 Dec-3 Jan in a single update RQ.

  • Continuous and Discontinuous Dates:

    • A request message can contain data for continuous and discontinuous dates as received from the hotel.

Multithreading:

  • API should support multiple parallel updates for a single hotel with different Product Types (A Product is a combination of 1 RoomType + 1 RatePlan).

  • Example of parallel updates to the HotelARIUpdate operation:

    • Update 1: RoomType A + RatePlan 1

    • Update 2: RoomType B + RatePlan 2

    • Update 3: RoomType C + RatePlan 3

Request#

HotelCode

RoomCode

RatePlanCode

StartDate

EndDate

Updates Made

RQ1

HTL1

DLX

STD

1-May-20

10-May-

20

Allocation=10,

1Adult=250USD

RQ2

HTL1

SUP

BAR

1-May-20

10-May-

20

Allocation=10,

1Adult=500USD

RQ3

HTL1

SUI

ADVP

1-May-20

10-May-

20

Allocation=10,

1Adult=1000USD

  • The partner should implement the API accordingly.

  • Alternate date updates allow a hotel to update multiple days with non-continuous dates in a single Update RQ.

  • Only 1 MealPlanCode can be supported for a given check-in date.

Last updated 3 months ago