Check the Hotel Release Notes for updates across all Hotel APIs.
Hotel Glossary
-
A platform that consolidates travel services, schedules, prices, and other details from multiple suppliers into a single interface.
-
Form of payment (FOP). Details of the type of payment to be used to pay for an offer, such as credit card information. Additional payment information is required to actually submit the FOP for payment for the offer.
-
In the JSON Hotel APIs, a request that sends all details of the room for which rules or booking is requested. Alternative is to send a reference payload request, which sends an identifier from a previous response instead of full details.
-
Global Distribution System, a computerized reservation system for booking travel. In the JSON Hotel APIs, content distributed by Travelport is noted as TVPT or Travelport.
-
IATA creates standardized codes used across air, hotel, rail, etc. to identify locations (cities and airports) and specific brands, amenities, characteristics, and so on. IATA is the International Air Transportation Association.
-
In the JSON APIs, the id object generally returns a short, internal, system-generated string, such as O1 for the first offer. Unique within the same response.
-
Unique six-digit alphanumeric number assigned by Travelport that identifies a reservation, e.g. JS7GH4. This online help uses the term locator code, which is sometimes called PNR or reservation identifier.
-
Maximum number of guests including adults and children per room.
-
Open Data Model. ODM is an open source, object-oriented data model developed by Open Travel, a cross-sector technology alliance for the travel community. The JSON APIs are based on the ODM model using either version 11 or version 12. See the JSON Hotel APIs Guide for details.
-
Search setting in offersPerPage that controls the number of offers returned in the initial Search response. When pagination is requested, all offers are cached on the server but only the number in offersPerPage is returned in the initial response. Request additional offers by sending the Pagination request. **Also controls whether search results are cached. Without pagination, results for a journey-based Search request are not cached. If your workflow uses subsequent transactions that reference a Search result, you must request pagination and invoke caching. See the Pagination API Reference.
-
A segment booked outside the JSON Hotel APIs, or added only with dates as a placeholder or retention segment. The segment is not linked to the supplier's system. See the Hotel Passive Guide.
-
Pseudo city code. A travel provider's identification code for the JSON APIs, provisioned from Travelport.
-
Passenger Name Record. Unique six-digit alphanumeric number assigned by Travelport that identifies a reservation, e.g. JS7GH4. This online help uses the more generic term locator code.
-
A special rate negotiated by travel agencies, companies, or other organizations. Requires a rate code to receive the rate.
-
The hotel itself.
-
A rate available to anyone, no rate code required.
-
A rate specific to a characteristic or organization, such as government, military, senior, corporate, etc.
-
The package of price, terms, and amenities for a specific hotel room. Each room type may have multiple rate plans depending on payment terms, refundability, and inclusions such as breakfast, parking, or wifi.
-
In the JSON Hotel APIs, a request payload that sends an identifier from a previous response. Alternative is to send all details, called a full payload request.
-
A confirmed booking with the carrier. A held booking is a booking that has not yet been ticketed. The terms booking and reservation are generally interchangeable.
-
Unique six-digit alphanumeric number returned for a successful booking, e.g. JS7GH4. For NDC the airline returns an additional locator code, which can be called the vendor locator code. Sometimes called a PNR and used to refer to the reservation as a whole, but because PNR is specific to GDS, this online help uses the more generic terms reservation or booking instead.
-
A type of passive segment that includes only dates. Used to keep reservation details active in the system after travel is complete, up to the dates of the passive segment. See the Hotel Passive Guide.
-
A standard category of room, such as a double room, king room, or suite.
-
One hotel room on a booking. For example, if you book 3 rooms, all reservation responses contain 3 segments. Each segment is returned as a separate offer.
-
The hotel that operates the property and makes property and rate details available through a booking platfrom such as Travelport or another aggregator.
-
In the JSON APIs, a unique long identifier for an entire response or an offer, product, brand in a response. These identifiers must frequently be sent in subsequent requests to refer to a previous response, offer, product, etc. Usually returned in Identifier/value for the referenced object and uses this example format: 3cecf1be-0b21-4881-8f33-ae11c8d7b708.
-
The JSON APIs return a tracking id in one and only one transactionId under the first top-level object of every response. This system-generated ID assists Travelport and customers with troubleshooting if needed. Developers can also send a custom traceId in the header as their own tracking number. See Transaction and Trace IDs.
A
F
G
I
L
O
P
R
S
T