Frequently Asked Questions

TripStax Content is an API that provides comprehensive Air content from various sources such as Global Distribution Systems (GDS), Low-Cost Carriers (LCC), and New Distribution Capability (NDC) providers.

TripStax stores booking data, profile data and financial data in our data processing engine, the TripStax Core. The TripStax Core consumes data from many sources to clean, enrich and store the data for use in the TripStax ecosystem – and beyond.

The TripStax Core is the data engine powering the TripStax modules, and data that is generated or enriched in the TripStax modules is stored in the TripStax Core.

Data is stored in Azure. Personal data is located in The Netherlands, in the EU. Non-personal data is stored in “the cloud”.

Yes.

We store booking data (air, hotel, car, rail, ferry and more…), profile data (companies and individuals), and finance data (fees, mark-ups, etc.).

Yes, the TripStax Core offers an API capability that can be used to connect tools and systems to interact with the TripStax Core.

The data in the TripStax Core comes from many sources for booking, profile, and financial data.
An important share of business travel data is still generated and captured via the GDS channel, not least for air bookings – TripStax collects booking and profile data from all the GDS systems. In addition to the traditional GDS channel, we also have feeds for NDC content, and LCC content, as well as direct data links from corporate booking tools and UK and international rail booking tools.
Beyond the connectivity with booking sources, the TripStax Core also has back-office integrations in place, allowing us to capture additional booking data – i.e. that is manually booked or booked off-channels and entered directly into the back-office system. The connectivity to the back-office also gives us access to financial data, e.g., mark-ups, fees, etc., to be able to power the TripStax Analytics module for complete reporting.
A final main type of data, profile data, is sourced directly from customers or from connections to the different GDS profile systems, as well as to other traveller profile tools.
Beyond the established connections, TripStax has strong integration capabilities to connect to new data sources and is also able to integrate structured data feeds from booking engines, profile tools, and back-office tools to power an agency with data from virtually any source.

Yes, we are connected to CBTs such as Concur, Cytric, Atriss, Vibe and more. The nature of the connectivity varies between systems but includes single-sign-on credential data, profile data, booking data and finance data.

We charge license fees per TripStax Module per month and transaction fees related to booking and profile data. A major part of the commercial proposition is the fact that we charge transaction fees only once, regardless of how many modules or external recipients consume the data.
This means that bookings are charged once per booking/PNR, and profiles are charged per profile per quarter – regardless of how many TripStax Modules or external tools are connected to the TripStax Core. If an agency currently uses tools from multiple providers, it is likely that the same booking or profile is paid for to multiple providers – the TripStax commercial model could make a huge difference. Note that if the TripStax Core is used to power non-TripStax technology, third parties may charge booking or other fees (unrelated to TripStax).

Yes, all modules are up and running in live environments, and the TripStax Core has processed millions of bookings and profiles. Current customers use anything from one Module to all Modules.

Our technology is currently in use around the world and in all continents; however, this does not mean that we have staff in every country or even every continent. The TripStax model and culture are fundamentally international, remote and collaboration oriented in their nature.

Microsoft Azure, MS SQL DB.

Microsoft .Net Core, Azure PaaS, Azure SQL DB, Angular, Microservices.

TripStax Content provides diverse Air travel content. This includes all GDS providers, NDC providers (like TravelFusion), and direct connections (like Lufthansa).

Yes, we are actively expanding our TripStax Content inventory. We are currently focusing on bringing in Hotels thanks to our recent acquisition of Hotelzon, but are also exploring additional content channels. For example, we are planning to partner with Jyrney to offer ground transportation.

TripStax Content offers normalized GDS content, Low-Cost Carrier content, and NDC content. This allows developers to deploy solutions more efficiently without needing multiple connections to different GDSs, aggregators, and airlines.

TripStax Content API gives access to all GDSs, LCC content from TravelFusion, and NDC content via direct connections as well as content aggregators like Kyte and TravelFusion. The Hotelzon API is also available today as a stand-alone API, soon to be accessible directly through the normal TripStax Content API.

Yes, comprehensive documentation is available to support developers in building the TripStax Content API.

Yes, agencies and developers can integrate TripStax Content API with their booking tools to access and manage bookable content.

Yes, the agency must have the right to access and book content from the respective suppliers and must be able to provide relevant details (e.g., credentials, PCC #, account #) to enable TripStax to activate the content.

No, TripStax does not support accessing Content features via the Portal. However, applications built on the TripStax API can be accessed via the Portal using Single Sign-On or a link.

TripStax Content API offers a normalized connection, which means developers can build once to access equivalent functionality from all suppliers. However, not all suppliers offer the same functionalities, so some specific connectivity might still be needed.

We're here to help! Please reach out to us on the TripStax Support Portal with details. Make sure to include the transaction ID (TID) of the request, so we can answer you effectively.

TripStax Content API allows for searching and booking travel, but it's up to the customer to link it with a suitable user interface.

Commercials include a license fee and a transaction fee per booking, as per the normal TripStax commercial model. Certain supplier fees related to transactions may be passed on.

The TripStax Content commercial model is based on a TripStax license fee and TripStax transaction fee. Any booking incentive or other supplier/content-related agreements would be contracted between the customer and the content supplier.

The TripStax Content proposition is access to normalised content via one API. The right to access the content via API must be secured by the customer (e.g. a GDS or supplier direct account). TripStax is not able to provide commercial terms.

The TripStax commercial model includes a transaction fee element. Suppliers may or may not apply transaction fees to bookings, as agreed between customer and supplier. TripStax is not able to guarantee specific TripStax terms.