Sample Request and Response

The following samples are a typical request and response for a hotel booking made through the Hotel service, which is accessed through the Universal API copy system.

Note: Before sending a sample request, it is recommended to make a ping request first to test connectivity to Universal API without calling an actual functional request.

Variables in the samples are in bold.

Sample Request

Requests include an HTTP header and a SOAP envelope and that contains the SOAP endpoint (including the requested service), gzip status, Travelport credentials, and XML request. All requests must be TLS encrypted.

HTTP Header

The HTTP header includes:

SOAP Envelope Containing Request XML

The following request is for a one-room hotel booking for one adult for a three-night stay. The hotel reservation is guaranteed with a credit card.

Sample Response

The sample response confirms the requested hotel reservation. The HotelReqRsp schema is used to define the XML. Universal API uses schema validation for requests. If your request schema is not valid, an error is returned in the response. Schema validation is enabled by Travelport, and cannot be disabled for individual transactions.

By default, rates are returned in the local currency of the hotel property. Free-form descriptive text from the supplier is also returned. If the reservation is the first booking for the trip, a new Universal Record is automatically created, with an Apollo PNR (booking record) contained within the Universal Record. If the reservation is added to an existing trip, a new PNR is appended to an existing Universal Record that already contains at least one PNR.

Because a Universal Record can contain booking records from multiple providers and suppliers, at least two types of record locators are returned in the response:

Depending on the provider and/or supplier, additional identifiers for this reservation may also be returned:

Transaction IDs uniquely identify the call and can be used for logging and debugging. Keys and references uniquely identify data within the call and can be used to maintain continuity of data in follow-on transactions. Credit card numbers and other identifying information are masked in the response.