One XML interface for all of your travel content
XX1 is our travel XML API tool which integrates travel content and inventory from various different supplier source systems and translates them into a unified XML format (content aggregation and/or translation). Our tool offers easy access to all major global distribution systems (GDS), central reservation systems (CRS) directly, hotel providers, car rental providers, rail providers as well as low cost carriers (LCC) through a single interface.
We provide the technology pipeline to all source systems (GDS & Non-GDS content) and make such content and inventory available to you through a single XML interface. In general all air/car/hotel content listed on GDS's such as Amadeus, Galileo/Apollo, Worldspan and Sabre is accessible at your fingertips via XX1, our travel XML API tool. We also offer a wide range of LCC's (low cost carriers), several rail provider, as well as a variety of hotel and car rental providers that we have integrated with directly.
Are you trying to integrate with one or multi GDS?
Are you planning to integrate with more than one GDS or other content source in the foreseeable future? Do not even bother thinking about integrating directly – use us and rest assured it will pay off. You do not need a lot of GDS experience on your own. Our workflows and explanations help you deal with the specifics of any reservation system. In any case our travel experts can assist with challenges you are facing.
Do you just need to retrieve PNR's without actually making bookings or looking for Super PNR capabilities? With our tool XX1 all these things and many more are possible as long as you have a commercial relationship with the 3rd party you want to access.
XX1 offers all clients one interface that looks the same for multi GDS sources. For our clients this means they need to maintain just one interface instead of every supplier system separately. Since we aim to be backward compatible this also means minimal amount of work to keep up with changes of 3rd party systems. Our travel XML API clients never have to worry about technology changes and/or migrations that happen frequently with 3rd party systems such as GDS. As an authorized developer for all GDS's for over a decade, we have the GDS and travel XML Interface expertise one can only wish for – sometimes even more than 3rd party systems themselves! There is no need to reinvent the wheel.
A new adapter/interface to any not yet integrated 3rd party system with a structured API (including but not limited to any XML provider or Navitaire's OpenSky or Newskies interface) can be developed in a matter of weeks. Our adapters are based on reusable components. Our high performance core provides an easy integration of new adapters. Interfaces such as EDIFACT, X 12, or TN 3270 complete the spectrum. This means that any travel content system can be integrated, even more complex systems such as TravelSky and others.
Why should I choose the PASS Travel XML API tool?
Our clients have confirmed that our technology has saved them a lot of time, money and stress. Clients who started out by themselves told us they wish they had known about us before.
No matter whether search, book, change, refund, or ticketing is required, the travel XML API XX1 manages it all. We always use the most reliable, most stable and best performing XML interface to the GDS's and other 3rd party systems. Be aware: It is not necessarily the case that the "latest" is also the "greatest". We know what is important and what is the best for you. We have proven to have a higher percentage of successful bookings than any other system.
Our XML is self-explaining, straight-forward and easy to understand. That is why it was chosen by IATA to become a world standard. For you this means that any investment in our XML schema is future proof for decades to come.
Our Travel XML API XX1 is a high performance, throughput optimized connector with an XML interface to many different reservation systems (Multi-GDS or Multi-Source). Many of our customers know exactly which GDS or other third-party systems they have to connect in which case. A special application case is e.g. our PNR retrieval application, which involves the retrieval of current PNR data from a specific GDS. But what if, in addition, several source systems are linked together (aggregation) and travel offers are to be offered to the user according to certain criteria?
With our intelligent iXX1, we have developed a business logic that goes beyond pure interface management. The PASS Travel Web API iXX1 provides complete microservices such as multi-source shopping service (incl. shopping cart management), booking service, exchange service etc. and integrates a rules engine that maps all "if-then" links and is closely linked to each business object. This greatly simplifies the handling of complex travel processes. Developing and maintaining an appealing, contemporary user interface is a major challenge. Again and again Apple, Google and Amazon come up with new gadgets. We want to save our customers from having to constantly renew the architecture and connection to the backend (travel provider) or to integrate and manage multiple sources themselves. In addition, there is no need for software developers with knowledge of old technology (XML), new technology (GUI applications) and travel know-how. Thus iXX1 facilitates the frontend development (GUI, App) but also the rule-compliant management of sources of the travel providers enormously.
ACCESS TO MULTI GDS VIA XML API TOOL
Easily use all the important global distribution systems (GDS) by integrating XX1's unified and simple XML API once.
ACCESS TO LCCS VIA XML API TOOL
Access to consolidators, low cost carriers (LCC) or access airline Central Reservation Systems (CRS) directly via XML API.
DIRECT ACCESS TO RESERVATION SYSTEMS
Direct access to supplier systems, such as airlines, CRS, hotel property management systems (PMS) or car rental.
COMPLEX FILTERING OPTIONS
XX1 offers several filtering capabilities in order to create the ideal solution for your business case and requirements.
ONE SUPER PNR FOR ALL TRIP DETAILS
Storing all trip details including air, non-air, online & offline bookings in one Super PNR (no passive segments needed).
USE YOUR OWN FRONTEND OR OURS
The standardized PASS/IATA XML allows future proof creation of your frontend (your own or use our frontend model kit).
FAST INTEGRATION OF NEW SUPPLIERS
Integration of any existing 3rd party system is only a click away and can be developed in weeks.
CONVERTION OF LEGACY INTERFACES
XX1 can convert any API (even airlines can migrate EDIFACT to state-of-the-art IATA-NDC).
XX1 is available on Linux and Windows with outstanding performance on both platforms.
FLEXIBILITY & SUPPLIER INDEPENDENCE
Take the driver seat & be in control of your content provider – be it commercial aspects or technical trouble, switch GDSs with one click.
REDUCTION OF SUPPORT- & MAINTENANCE COST
Maintain only one backwards compatible interface – we will ensure that interface changes of GDS and 3rd parties will be seamless to you.
OVER A DECADE OF EXPERTISE
Build your future on a stable foundation. We have been authorized developer for GDS since the year 2000. APIs are built to last.
CFOS AND TECHNICAL FOLKS
- Enjoy the flexibility to be independent from your content provider: Facing technical problems with a back-end system? Trying to find a better commercial deal with another 3rd party provider? A seamless switch, full or in parts to a different GDS is only a click away.
- Savings and budget planning security for implementation, support and maintenance – one XML interface, developed once – instead of the need to develop and maintain multiple, constantly changing interfaces to all different travel content sources.
- Time to market: Fast integration of any not yet available travel content provider.
DECISION-MAKERS AND IT EXECUTIVES
- Enjoy independence of frequently changing GDS interfaces. There is no need to constantly adapt to a new interface.
- PASS is experienced in IT and travel related systems since 1981. PASS was first to introduce XML into the travel industry in 1999 and has since gained significant GDS experience on all major GDS's.
- XX1's XML format is on the verge of becoming a world standard as IATA's resolution 787 NDC proposal is based on PASS XML schemas.
- XX1 is a proven and mature system in production since the year 2000. The clients of XX1, our travel XML API tool, serve 75% of the world's corporate travel market.
3 reasons to choose PASS XX1
If your technology vendor is also your content provider, your platform is hooked to one GDS and any future change will be a problem. You will need a migration path and have to solve a technical challenge along with a commercial one.
The PASS Travel XML API, however, allows you to simply switch on other GDSs or 3rd parties now or later. Our clients have been able to switch from e.g. Travelport to Amadeus in the blink of an eye. Furthermore, should an airline drop out of a GDS or install a marketing fee (compare e.g. Lufthansa), our Travel XML API makes you more flexible. All in all, you take advantage of enhanced business continuity and a solid ground on which to negotiate GDS deals in the future.
2. Expansion made easy
Many of our clients start with a single GDS and expand later as they grow. The addition of another GDS or 3rd party is reduced to primarily a commercial agreement with such provider. Once we have set up those credentials, you are ready to go. If at all, your technology only needs minor adjustments.
3. Backwards compatibility
While GDSs usually change their API frequently, we keep up with these changes and make them transparent for our clients while providing little to no impact for them. In 2015, for the first time in five years we introduced a schema adjustment due to the integration of ancillary features. How many other interfaces remain constant for half a decade?
Several GDS, several interfaces
As seen on the bottom of the architecture, XX1 is connected to various travel service provider included but not limited to GDSs, LCCs, hotel property management systems, rail provider and car rental companies. Each of these provider 'speak' their own 'language'. Sabre for instance has a Sabre webservices interface and provides messages such as Bargain Finder Max (BFM). An alternative way is to communicate with SDS messages to Sabre. Amadeus also has a webservices interface or an API V2 interface (supposed to be decommissioned). A similar message such as BFM on Amadeus would be Masterpricer. Travelport has a number of historically grown interfaces such as Galileo/Apollo webservices or XML Select, Worldspan DIR, XML Pro (an actual Pass product), or universal API (uAPI). Airline carriers speak EDIFACT. EDIFACT is supposed to be replaced by NDC which is a schema IATA adopted from PASS.
LCCs sometimes use a ticketless version of the GDS/CRS, or they have their own system. Some also use Navitair's OpenSkies/NewSkies reservation system. LCC aggregators (such as Travelfusion, or Elsy Arres) sometimes employ screen scraping of the respective airline websites in order to provide a structured interface.
Hotels and car rental companies usually have their home grown systems derived from the Open Travel Alliance (OTA). Rail provider usually have entirely their own system and there are only a few aggregators such as SilverRail.
One XML API for all GDS
Out of this multitude of different 'languages' and interfaces, XX1 creates one XML data interface or API (seen on the top of the architecture) which looks the same across all these different content and inventory sources. As you can imagine it has been a huge undertaking to create one single globally accepted XML schema from all this different 3rd parties. This is why the XX1 XML schema has become a worldwide standard in the industry adopted by IATA.
Modules for filtering, scripting and storing of booking information
Besides the translation of any 3rd party specific interface carried out by the XSLT transformation engine together with the transaction engine as seen in the middle of the architecture, XX1 also employs filters to add features, apply logic or modify results.
The XX1 scripting engine allows to model and adapt to different business process workflows.
The optional XX1 Super PNR database stores the complete booking record including the (different) source(s) where it was booked. The optional profile database allows storage, maintenance and usage of traveler profiles. One- or bi-directional profile synchronization with GDSs or other 3rd party profile databases is possible. Pass-through commands such as a cryptic message complete the spectrum.
Read more about the architecture of Travel XML API tool XX1.
The modular structure allows the usage of XX1 in many different contexts. XX1 powers corporate booking tools and technology providers such as nuTravel or Amadeus E-Travel, as well as leading travel management companies (TMC's) to shop, book, retrieve, change and ticket itineraries regardless of the inventory management system (GDS/CRS) behind.
In addition, our travel XML API tool also supports automated file finishing and quality control applications. This could be an automated check if there is a better trip option available than the one booked. As prices can drop unexpectedly, most organizations and TMC's carry out such auto-checks within the 24 hour "void" window or even later in case prices dropped to a level that a re-booking is cheaper, even if the change fee is to be applied.
Medical, clinical and security services
Finally, XX1 supports companies such as International SOS, FrontierMedex, or OnCall International who provide integrated medical, clinical and security services to nearly all Fortune 500 organizations and beyond. In this case XX1 retrieves and provides the actual trip data of the travelers (the passenger name record "PNR") from the GDS/CRS. Knowing who travels where and when allows mentioned companies to apply their security data and information personalized and individually right to the target – the traveler. Updating vaccinations for certain trips and information about unrests or potential unsafe areas, helps keeping the traveler – the ultimate asset of any organization – safe and healthy.
Travel business intelligence
With our queue management tool we can assemble PNR easy from different reservation systems. Thereby a comprehensive real-time-reporting is enabled. Consequently you can arrange your travel management global and proactive.
These are just some example business cases of a potential usage of the XX1 XML API. Any time you need to establish a connection to a GDS/CRS or other travel related 3rd party, it makes sense to evaluate the usage of the travel XML API tool as the common and most used integration middleware platform – be it PNR retrieval, shopping/booking/ticketing or any other use case.
In most cases yes. Our main focus is to provide the technology – so in other words, we provide the technical pipeline for you to access any 3rd party. We are authorized and certified developers for all major GDS. However, certain 3rd parties require you to have your own relationship with them in order to access their content and inventory. Thus with very little exceptions you need to have a commercial agreement with the respective 3rd party you want to use.
However, in case you already have a pseudo city code (PCC), this should be a straight forward process. GDSs also may require you to certify your application and/or authorize content from other sources.
We also do not provide fulfillment services.
Yes, you can add additional content sources at any point in time subject to restrictions mentioned above (agreement with 3rd parties & authorization/certification).
We have existing connectors to all major GDS, that can be "switched on" for you as you might need them. You will save a lot of time and effort by integrating with us. Even only one GDS may pay off as usually there will be no need to keep up with frequent format changes of GDSs or the requirement to integrate a new interface. The moment you add a second source and become multi GDS your savings even further materialize.
No, you do not.
This is one of the major benefits of XX1. You can access all kinds of content sources, but only need to implement once – with us! We take care of the many changes which are put in place by 3rd parties.
The only time you need to adapt to changes is when there is a major new release with additional features which you may want to take advantage from.
If I want an adapter to a certain content provider of my choice which I cannot find on the list – what do I do?
You contact us. We might have some 'unofficial' adapters which we have not officially released yet. In case we do not have the requested adapter to a certain content provider, we can implement almost every adapter in a timeframe between 4-6 weeks as long as there is a structured interface.
We have integrated around 20 new adapters annually over the past years. If there is no structured interface we might still be able to integrate such interface but we need to analyze. We usually do not provide website screen scraping as there is no robust enough and affordable technology available to effectively provide and maintain such interface. However, we have integrated a couple of LCC aggregators who their end partly utilize screen scraping of 3rd party websites.
This was tested several times by our customers and we always came through with flying colors in. We can assure you that you will not realize any performance impact due to our technology.
Sometimes we even have to manually force delays in order to give our partner systems time to react. If you are still concerned and operate mega business there are also special versions available for high performance environments.
If you have a Pseudo City Code (PCC) and/or are authorized to utilize a specific 3rd party system or GDS, you will sign an agreement with PASS. We can provide you with a no risk grace period (other than a setup fee).
You can start implementing with XX1 in a matter of days. We offer support through our XX1 helppage and you may contact our experts through our helpdesk.
Here you can find a detailed overview of which XX1 standard messages are supported by which third-party system. Details on the individual messages can be found on our technical documentation page.
|Air Messages||Abacus||Amadeus||Apollo||Galileo||Sabre||Worldspan||Axess||ElsyArres||LFP||TravelFusion||Alamo||Avis||CarTrawler||Dollar||El Monte||Europcar||Hertz Balearic Islands||Hertz USA||Holidayautos||Mietwagenmarkt||National||Sixt||Thrifty||THL Rentals||Qantas||Center Parcs||Corporate Rates Club (CRC)||eHotel||GTA||Booking.com||HotelBeds||HRS||Jonview||Pegasus||Utell||Northstar TM||AirArabia||Bahrain||Condor||FlyDubai||GoAir||Indigo||Ocean||SpiceJet||TUIFly|
|Fare Messages||Abacus||Amadeus||Apollo||Galileo||Sabre||Worldspan||Axess||ElsyArres||LFP||TravelFusion||Alamo||Avis||CarTrawler||Dollar||El Monte||Europcar||Hertz Balearic Islands||Hertz USA||Holidayautos||Mietwagenmarkt||National||Sixt||Thrifty||THL Rentals||Qantas||Center Parcs||Corporate Rates Club (CRC)||eHotel||GTA||Booking.com||HotelBeds||HRS||Jonview||Pegasus||Utell||Northstar TM||AirArabia||Bahrain||Condor||FlyDubai||GoAir||Indigo||Ocean||SpiceJet||TUIFly|
|Car Messages||Abacus||Amadeus||Apollo||Galileo||Sabre||Worldspan||Axess||ElsyArres||LFP||TravelFusion||Alamo||Avis||CarTrawler||Dollar||El Monte||Europcar||Hertz Balearic Islands||Hertz USA||Holidayautos||Mietwagenmarkt||National||Sixt||Thrifty||THL Rentals||Qantas||Center Parcs||Corporate Rates Club (CRC)||eHotel||GTA||Booking.com||HotelBeds||HRS||Jonview||Pegasus||Utell||Northstar TM||AirArabia||Bahrain||Condor||FlyDubai||GoAir||Indigo||Ocean||SpiceJet||TUIFly|
|Hotel Messages||Abacus||Amadeus||Apollo||Galileo||Sabre||Worldspan||Axess||ElsyArres||LFP||TravelFusion||Alamo||Avis||CarTrawler||Dollar||El Monte||Europcar||Hertz Balearic Islands||Hertz USA||Holidayautos||Mietwagenmarkt||National||Sixt||Thrifty||THL Rentals||Qantas||Center Parcs||Corporate Rates Club (CRC)||eHotel||GTA||Booking.com||HotelBeds||HRS||Jonview||Pegasus||Utell||Northstar TM||AirArabia||Bahrain||Condor||FlyDubai||GoAir||Indigo||Ocean||SpiceJet||TUIFly|
|PNR Messages||Abacus||Amadeus||Apollo||Galileo||Sabre||Worldspan||Axess||ElsyArres||LFP||TravelFusion||Alamo||Avis||CarTrawler||Dollar||El Monte||Europcar||Hertz Balearic Islands||Hertz USA||Holidayautos||Mietwagenmarkt||National||Sixt||Thrifty||THL Rentals||Qantas||Center Parcs||Corporate Rates Club (CRC)||eHotel||GTA||Booking.com||HotelBeds||HRS||Jonview||Pegasus||Utell||Northstar TM||AirArabia||Bahrain||Condor||FlyDubai||GoAir||Indigo||Ocean||SpiceJet||TUIFly|
|Ticket Messages||Abacus||Amadeus||Apollo||Galileo||Sabre||Worldspan||Axess||ElsyArres||LFP||TravelFusion||Alamo||Avis||CarTrawler||Dollar||El Monte||Europcar||Hertz Balearic Islands||Hertz USA||Holidayautos||Mietwagenmarkt||National||Sixt||Thrifty||THL Rentals||Qantas||Center Parcs||Corporate Rates Club (CRC)||eHotel||GTA||Booking.com||HotelBeds||HRS||Jonview||Pegasus||Utell||Northstar TM||AirArabia||Bahrain||Condor||FlyDubai||GoAir||Indigo||Ocean||SpiceJet||TUIFly|
|Profile Messages||Abacus||Amadeus||Apollo||Galileo||Sabre||Worldspan||Axess||ElsyArres||LFP||TravelFusion||Alamo||Avis||CarTrawler||Dollar||El Monte||Europcar||Hertz Balearic Islands||Hertz USA||Holidayautos||Mietwagenmarkt||National||Sixt||Thrifty||THL Rentals||Qantas||Center Parcs||Corporate Rates Club (CRC)||eHotel||GTA||Booking.com||HotelBeds||HRS||Jonview||Pegasus||Utell||Northstar TM||AirArabia||Bahrain||Condor||FlyDubai||GoAir||Indigo||Ocean||SpiceJet||TUIFly|
|Miscellaneous Messages||Abacus||Amadeus||Apollo||Galileo||Sabre||Worldspan||Axess||ElsyArres||LFP||TravelFusion||Alamo||Avis||CarTrawler||Dollar||El Monte||Europcar||Hertz Balearic Islands||Hertz USA||Holidayautos||Mietwagenmarkt||National||Sixt||Thrifty||THL Rentals||Qantas||Center Parcs||Corporate Rates Club (CRC)||eHotel||GTA||Booking.com||HotelBeds||HRS||Jonview||Pegasus||Utell||Northstar TM||AirArabia||Bahrain||Condor||FlyDubai||GoAir||Indigo||Ocean||SpiceJet||TUIFly|
Structure of XX1
PASS XX1 is the high-performance platform to shop, book, retrieve, change and ticket itineraries in any major CRS and GDS through XML. Interfaces, like EDIFACT, X 12, TN 3279, Fares, Northstar or direct access to airlines and respective exchange of messages and information complete the spectrum of functionality.
The travel XML API primarily consists of:
- High performance transaction server for
- Data distribution
- Document exchange
- Business procedure processing
- Normalized messages and business functions
- XML BODs ("XML business object documents") according to Open Applications Group Integration Specification (OAGIS) recommendation
- Document root node designates business function/message
- BODs are defined and published through XML schema
- Through XML transaction control headers ("TC") directed message flow
XX1 provides a highly modular server design, with comprehensive support for adding technologies and implementing new standards. The XX1 Client SDK (see below) allows for integration of any type of data source or legacy system in short time frames at moderate costs.
The XX1 Server software was entirely written in ANSI C++ and is available for Windows and Linux platforms.
The XX1 Client SDK components communicate with XX1 Server through a SOAP interface. The XX1 Server SDK allows you to build custom interfaces other than SOAP, for example MQSeries, RPC, Corba or DCOM. Client applications usually reside on remote machines. The XX1 Client SDK is available for C/C++, dotnet, ActiveX, and Java.
A filter mechanism is available which allows configuring multiple filters in XX1, to add features, logic or additional data from/to requests and responses. Example: A security filter can be configured which implements access control in XX1.
Different XSLT transformation engines can be configured for business logic data transformation purposes to match requirements regarding performance, compatibility. A selection of currently available XSLT transformation engines:
- MSXML 4/6 (Windows)
- Oracle 9i (Unix)
- libxslt (Linux)
SOAP API (XML)
Different types of interfaces are configurable to communicate with XX1. SSL encryption and certificate handling is supported. A selection of currently available XX1 interfaces:
- SOAP/SOAPSSL: default for travel backend XX1
- HTTP/HTTPS: can run as webserver accepting HTTP GET/POST and returning HTML pages
- EDIFACT: can accept and return EDIFACT format for certain functionality
- Scheduler interface: can trigger time- or event driven activities on XX1
The XXE transaction engine is the high performing, C implemented core of XX1 which integrates the different configurable modules and offers additional common functionality, e.g.:
- XML DOM processing
- XPATH processing
- Data format conversion (date, time, …)
- XML table lookup
The XX1 super PNR component allows to book travel segments from different provider systems into a common meta booking record called super PNR. Parts of the SPNR booking record are stored independent of any provider system in a database maintained by the SPNR component.
XX1 pricing aims to provide a low entry barrier but also attract heavy users while the software can be hosted in-house or deployed
|Application hosting||License & maintenance||Source code|
|Pricing model||Monthly application license- & hosting fee with an number of free transactions||Upfront license annual maintenance fee, regardless of amount of transactions||Purchase source code license (only certain business models not to compete with us)|
|Fits best for||Everybody. We offer various pricing models based on XML transactions, term, etc.||Heavy user with high transaction volume||Organizations with GDS know-how to maintain and extend XX1 to meet their own requirements|
|Data center||We (or you)||You (or we)||You|
|Installation||We||You or we||You|
|Time-to-market||Integration in days if major GDSs or existing content providers are accessed, and provided you are authorized to access content & inventory from such 3rd parties.||Integration in days if major GDSs or existing content providers are accessed, and provided you are authorized to access content & inventory from such 3rd parties.||Integration in days if major GDSs or existing content providers are accessed, and provided you are authorized to access content & inventory from such 3rd parties.|
|Benefits||Low fixed costs||High transaction volume and fixed costs||Independence|
|Software support & maintenance||Helpdesk access included. Reported bugs to be resolved according to our priorities. Optional maintenance contract with Service Level Agreements (SLA).||Helpdesk access included. Reported bugs to be resolved according to our priorities. Optional maintenance contract with Service Level Agreements (SLA).||Optional|
|SLA response||During business hours||During business hours||N/A|
|SLA costs||To be negotiated with management||To be negotiated with management||N/A|
|Costs||Starting at $1,500 (month)||$300,000/$100,000 (year)||Negotiable|
|License term||flexible (5 year terms provide best value for money)||flexible (5 year terms provide best value for money)||Perpetual|
|Includes||All available adapters||All available adapters||All available adapters|
|Optional pricing model||Per PNR transaction (with monthly minimum)||Only use specific messages / content provider||On request|