Explore the key bottlenecks of travel supplier integration.
Explore the key bottlenecks of travel supplier integration.
Integrate suppliers’ flight APIs.
Map search results from different suppliers.
Build a customizable set of integration modules.
Create a responsive UX and the demo website.
Working on this platform, our team wanted to create a customizable solution that would work for different types of travel businesses. To make it happen, the team gathered data from travel-related engagements, interviewed clients and members of product teams. This helped pinpoint the bottlenecks and challenges that developers face building search and booking software for travel businesses. One of the key difficulties is working with legacy SOAP APIs that GDSs use and integrating them into search and booking engines.
Our team started with flight API integration. The team used GDS APIs as well as APIs by other travel product suppliers to access authorization, flight and fare search, booking, and PNR management. The current roadmap of the project includes further integrations with hotel bed banks and expanding flight content and ancillary access.
Different GDSs and suppliers send search results using their own unique data models. Since the platform integrates multiple suppliers with intersecting inventories, these results must be mapped to each other. Additionally, the data models that suppliers use are often cryptic and difficult to understand for an ordinary travel professional. The AltexSoft team designed a travel domain data model. It maps and presents results coming from various suppliers in a single format that can be understood by anyone, regardless of their technical skill.
Our goal was to make the platform agnostic to the unique business logic of search, booking, and commission engines that travel players use. This means that the supplier connections can be easily integrated into existing systems of travel businesses. The platform integrates complex supplier APIs, providing RESTful JSON-based connection to the client’s business logic. The platform's modular architecture allows travel businesses to choose which types of supplier services they need to operate, including authorization, search, booking, and PNR management. The platform is built using .NET Core 3.1.
To demonstrate the platform’s functionality, we’ve created a client-facing website. The design is minimalistic and has various navigation elements, like a flight ticket search box, dropdown calendar, and a text-based chatbot capable of search and booking. The interface was created using Vue.js and can be further customized. The team used a CI/CD pipeline for automated regression testing. The demonstration website together with the platform modules are deployed on Azure Cloud.