Content Providers and Definitions

Universal API uses several levels of booking records and booking data to identify and record data for a single journey.

Providers

Universal API obtains data directly from providers, which include Travelport Systems (Global Distribution Systems (GDSs)) and other database systems. A Passenger Name Record (PNR) (ProviderLocatorCode) is created by a provider when a travel segment (air, vehicle, or hotel) is booked and saved (end transacted). One or more travel segments can be included in a PNR.

In the current release, the following providers are enabled for one or more services and functions:

Note: As content hubs, RCS and ACH support access to multiple carriers. ACH supports connectivity with a number API-connected carriers, including Low Cost Carriers (LCCs);RCS supports connectivity with several rail carriers. Therefore, provisioning can support access not only to ACH or RCS as the provider, but also to specific carriers available through these hubs.

Additional providers and carriers will be added in future releases. Also, please note that the current release does NOT support all functionality by all of the listed providers. Service-related topics include a list of providers that partially or completely support the functionality described in that topic.

Note: The term provider is distinct from travel provider, which includes agencies, online travel companies, and other organizations that offer travel-related services directly to travelers.

Currently Supported Functionality by Provider

Functionality

Galileo

Apollo

Worldspan

Axess

ACH

RCS

Air

 

Low Fare Shopping: Air

 

Branded Fares

   

Ancillaries

   

Hotel

 

 

Vehicle

 

 

Rail

 

Low Fare Shopping: Rail

 

Availability: Rail

         

Please note that all functionality is not universally available for all supplier and providers. Please see the Exceptions section of each topic for details about provider- and supplier-specific functionality.

Suppliers

Providers obtain data directly or indirectly from suppliers, which include airline carriers, hotel chains, rental car agencies, and other vendors.

In addition to PNR record locators, individual suppliers may include confirmations or other vendor-specific confirmation codes or other locators for their booking data (SupplierCode). Supplier codes are generated by the supplier and are stored for reference. However, unlike PNRs, supplier codes are not searchable in Universal API.

In addition to suppliers available through Galileo, Apollo, Worldspan, and Axess the following carriers are available through the Airline Content Hub (ACH) and Rail Content Service (RCS).

Note: Some ACH and RCS carriers may choose to apply geographical and/or point-of-sale restrictions to their content. Some carriers may also charge a booking fee.


For a more complete list of functionality available from various ACH carriers, see ACH Carriers Functionality. Because functionality for carriers may be subject to change, always confirm functionality directly with the ACH carrier before implementation.


ACH Carriers

Important: ACH has a session timeout limit of 1 hour. However, ACH carriers often have a lower session timeout limit. While API-connected carriers do not publish timeout values, a good rule of thumb is to expect a session timeout limit of 15-20 minutes for an ACH carrier.

Supplier

Code

Base

Air Canada

AC

Canada

Calafia

A7

Mexico

easyJet

U2

United Kingdom

IndiGo 6E India

Jambojet

JX

Kenya

Jet2

LS

United Kingdom

Jetstar JQ Australia

RyanAir

FR

Ireland

Southwest Airlines

WN United States

Tigerair

TR

Singapore

TigerAir Taiwan

IT

Taiwan

Transavia

HV

Netherlands

Transavia France

TO

France

RCS Carriers

Supplier

Code

Base

Amtrak

2V

United States

SNCF

2C

France

Via Rail 2R Canada

Travelport System (GDS) Rail Carriers

Supplier

Code

Base

Eurostar

9F

France

AccesRail

  • DB - Deutsche Bahn

  • EJR - East Japan Rail Company

  • JR Kyushu

  • Michigan Flyer

  • National Express

  • NS - Dutch Railway

  • ÖBB - Austrian Railways

  • Renfe

  • SJ - Swedish Railways

  • SNCB - Belgian Railways

  • Thalys

  • VIA Rail Canada

9B

Canada

Speed Alliance

  • Renfe Spain

  • WESTbahn Austria

5W

Austria

Over 70 air-rail codeshares

 

 

Air-Rail Codeshares

An air-rail codeshare means a code-share with at least one sector that includes a train segment booked as a flight.

As the industry and airlines move further into air/rail arrangements, more markets are opening to this arrangement and IATA station codes numbers have grown from 100 in 2000 to over 800 in 2015. The change from air / air interlining to air / rail codeshare has mainly been driven by the rise in high speed rail in these markets and the building of railway station at airports improving airport access but also linking airports to more than one city. The arrival of high speed rail in certain markets Air / Rail is also referred to as multi modal where one sector is operated by a plane and the onward or arriving sector is operated by a train (normally high speed).

As part of the code share arrangements, the air and rail suppliers work out IATA rail station codes, ATPCO fare filing and tax exemption arrangements, seat assignment rules, passenger types, boarding pass collections, connection guarantees, timetable data and changes, and similar understandings. These inclusions will be communicated to the passenger as part of the normal booking process.