aggregator: A platform that consolidates travel services, schedules, prices, and other details from multiple suppliers into a single interface.
F
form of payment: 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.
full payload: In the APIs, a reqeust that sends all details of the offer or flight/s to be shopped, priced, added to the workbench. The alternative is to send a reference payload request, which sends a reference to an offer in a previous API response instead of full details.
G
GDS: Global Distribution System. A GDS aggregates and distributes air, hotel, and car rental content such as schedules, fares, and upsells. In the APIs, GDS content is distributed from Travelport.
I
IATA code: 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.
id: In the APIs, the id object generally returns a short, internal, system-generated string, such as O1 for the first offer. Unique within the same response.
L
locator code: 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.
O
occupancy: Maximum number of guests including adults and children per room.
ODM: 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 APIs are based on the ODM model using either version 11 or version 12. See the APIs Guide for details.
P
pagination: 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.
passive segment: An air segment booked in a system outside the Travleport GDS. Adding a passive air segment to a booking maintains all travel details as part of the complete itinerary.
PCC: Pseudo city code. A travel provider's identification code for the APIs, provisioned from Travelport. Used to determine access and other settings in the APIs for your company.
PNR: Passenger Name Record. Unique six-digit alphanumeric number that identifies a booking, e.g. JS7GH4. Sometimes used to refer to the booking record itself. Because the term PNR is specific to GDS, this online help uses the more generic term "reservation locator".
private rate: A special rate negotiated by travel agencies, companies, or other organizations. Requires a rate code to receive the rate.
property: The hotel itself.
public rate: A rate available to anyone, no rate code required.
R
rate category: A rate specific to a characteristic or organization, such as government, military, senior, corporate, etc.
rate plan: 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.
reference payload: In the APIs, a request that sends an identifer referring to the offer from a previous response instead of full itinerary details. The alternative is to send a full payload request, which sends all offer details.
reservation: 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.
reservation locator: Unique six-character alphanumeric code 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 booking record as a whole, but because the term PNR is specific to GDS, this online help uses the more generic terms "booking" for the booking record and "reservation locator" for the six-character code.
retention segment: 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 Passive Guide.
room type: A standard category of room, such as a double room, king room, or suite.
S
segment: A flight or flights under one flight number. One flight equals one segment. A segment could have multiple flights if the flight number remains the same, which happens if a flight makes a stop without changing planes.
supplier: The hotel that operates the property and makes property and rate details available through a booking platfrom such as Travelport or another aggregator.
system-generated identifier: In the APIs, a unique identifier for specific, unique data, such as an entire response or an offer, product, or brand in a response. These identifiers must often be sent in subsequent requests to refer to a previous response, offer, product, etc. Usually returned in Identifier/value for the referenced object. Example format: 3cecf1be-0b21-4881-8f33-ae11c8d7b708. See the APIs Guide.
T
transaction ID: A tracking id returned in the transactionId object under the first top-level object of every response in the APIs. This system-generated ID assists Travelport and customers with troubleshooting if needed. In addition, developers can send a custom traceId in the header as their own tracking number. See Transaction and Trace IDs on the General menu.