Overview

OTA API Specs

Overview

Agoda OTA API is an interface that let you manage your rates and availability for Agoda. This document will help you understand how to send the requests to OTA API and how to read the response messages.

OTA API Versions

Currently Agoda supports two versions of the OTA sepccifications which are:

  • 2013A
  • 2015B

Functions

Please see below the available requests and their descriptions.

RequestResponseDescription
OTA_HotelAvailNotifRQOTA_HotelAvailNotifRSUpdate the availability restrictions for one room type in a single hotel. The restrictions include closed for sale, closed to arrival, closed to departure, length of stay.
OTA_HotelBookingRuleNotifRQOTA_HotelBookingRuleNotifRSUpdate the booking rules for one room type in a single hotel. The booking rule include min advance purchase, max advance purchase, or absolute cut off date.
OTA_HotelRateAmountNotifRQOTA_HotelRateAmountNotifRSUpdate the availability and rates for one room type in a single hotel. The rates include availability, rates, taxes, fees, meal plan, and cancellation policies.

Background

In order for you to understand the terms and descriptions of elements we used in OTA API, please find the details of the important elements here.

Rate Plan

To be added

RatePlanCode

To be added

Room

To be added

InvgtypeCode

Channel

To be added

End Points and Authentication

End Points

In order to connect to Agoda OTA API, please use the end points as specified below. Please noted that we offer different end points for each version.

Authentication

The Agoda OTA API requires HTTP Basic Authentication which is the encryption (base64) of the "username:password". The authentication must be available in the header of the request.

Normally the rest API application will provide the encryption for you. Just enter the username and password you receive from Agoda.