Overview
The following article will give you an overview of the flight search performed out of TripBuilder within the integrated supplier systems and how the search results can be influenced.
FAQ
Q: How can the feature be activated?
A: The activation of this feature is managed by Nezasa. To enable it, please contact our support team or your designated customer success manager to access the feature flag under Distribution Channel > Planner > International Flights > Integration Type. Nezasa team will ensure the Integration Type configuration is set to External Provider.
Please note: Before enabling the feature, you should have already shared your GDS connection credentials with Nezasa for configuration in TripBuilder. |
Q: How can I access GDS flights via the TripBuilder API?
A: The same configuration that determines whether flights are displayed in Planner also regulates their accessibility via the Planner API.
Know more: Check the Planner API article for further information on how to programmatically retrieve flight details. |
Q: Which GDS systems can be connected?
A: Within the TripBuilder system, different flight consolidators are integrated, such as AERTiCKET and SoftConEx. Find the overview of all supplier integrations here.
Via AERTiCKET, SoftConEx, different GDS systems can be connected to TripBuilder.:
- SoftConEx
- GDS connections: Amadeus, Saber, Travelport and Farelogix, Navitaire, as well as increasingly in Direct Connects. Find more details here.
- AERTiCKET
- GDS Connections: Amadeus, Sabre, Galileo, Worldspan and Fairlogix. Find more details here.
Q: What happens if 2 GDS systems are connected via SoftConEx or AERTiCKET? Will duplicate offers be returned?
A: Yes. The same flight can and will be returned multiple times if found in different GDSs. For example, if 2 GDS systems are connected, and the same fare appears in both, we display both.
However, this can be prevented with a set of content rules within the TripBuilder system.
Find more information about content rule setting within TripBuilder, here.
Q: How does our duplicate fare filter work? Which fare is taken, the cheapest one?
A: The duplicate fare filter works by checking the airline designator, flight number and departure time for each leg in the segment and checking whether there are other flights with the exact match. This works because a given flight number for an airline is valid at only one point in time (the flight numbers can be reused, though). Our duplicate fare filter will take the cheapest one.
Q: What content filters are available for flights within TripBuilder?
A: The Content Rule feature enables the delimitation of content by creating an individual rule set to determine the content of the transportation/flights. The search results can be infused by setting specific content rules for transportation/flights.
The following rule definitions are currently available:
Example:
Find more information about content rule setting within TripBuilder, here.
Q: What filters/rules does the consolidator offer?
A: Filter and rules can directly be applied within the consolidator connections. Please contact your dedicated customer success managers at AERTiCKET or SoftConEx for more details.
Q: Does the Passenger Name Record (PNR) for a flight booked with TripBuilder contain a reference to the itinerary?
A: Yes, during the flight booking process, TripBuilder includes a reference to the itinerary that the flight is a part of. Subsequently, when you access the PNR for that booking, you can find this information along the remarkElement\freeText node path. The value of this field starts with a constant prefix NEZASA-REFID, followed by the itinerary ID.
Comments
0 comments
Article is closed for comments.