Universal API aggregates content from multiple sources including GDSs (air/vehicle/hotel), low cost carriers, high-speed rail, merchandising, and non-GDS Hotel through a single API connection. By providing a single API, Travelport enables developers to code once and gain access to multiple content sources, decreasing the time-to-market for an application. Superior customer support and a single contract with Travelport also simplify the process.
Travelport Universal API:
- Reduces costs associated with learning and maintaining multiple APIs.
- Allows companies to create richer travel applications with better content.
- Provides access to merchandising content from multiple sources (ATPCO, Direct Connect, Low Cost Carriers).
- Streamlines and improves application performance by reducing the number of calls necessary to complete end-to-end workflows.
- Allows compliance with EU recommendation to provide high-speed rail alternatives where one exists, alongside a traditional air response.
Users can choose to augment their current application suite by adding features and content, integrated through Universal API. Or, users can implement against Universal API as a complete end-to-end solution.
Demo Site
The Travelport Demo site has been created to stimulate new ideas and help you develop new applications to stay ahead of the competition. Through this demo site, we are able to showcase new content and functionality with code that’s ready to use.
Architecture
The Universal API is the one API that connects you to multiple content sources. The diagram below shows how Universal API gets that content and supplies it back to our users (Points-of-Sale). Not only does Universal API provide access to our own Travelport GDSs, but it also provides access to a set of “hubs” that allow you to gain access to non-GDS air and hotel content. Travelport actively continues to build out this model so we can provide the most current, relevant content for our Universal API.
The Universal API schema is normalized so that it can be used across any of the content providers. Differences in functionality between providers still needs to be accounted for, because there may be differences between what each provider supports. For example, a Low Cost Carrier Air Shopping transaction is simpler than an Air Shopping transaction using a GDS provider.
Standards and Protocols
Universal API conforms to the following industry standards and protocols.
|
Message Envelope |
SOAP 1.1 |
|
Message Transfer |
HTTP 1.1 |
|
Encryption |
TLS 1.2 Important!Travelport does not support TLS 1.0 or 1.1. |
|
Web Service Description Language |
WSDL 1.1 |
|
Data Transfer |
XML 1.0 |
Feedback / Support
