NEZASA TRAVEL PLATFORM v349
We are happy to announce our latest TripBuilder release. Please see these release notes for the most significant changes. Let us know if you have any questions, feedback, or ideas for features or improvements!
By email: [email protected]
Via support portal: https://support.nezasa.com/
Via BucketList: Available in TripBuilder's Cockpit at the Resource Centre
.COCKPIT
View FX rates on components from the Cockpit Copilot
Cockpit Copilot allows to retrieve FX rate information, when currency conversion occurs.
Suggested prompt - ‘Copilot, provide the foreign exchange rate applied for all services booked on the itinerary.’
.APIs
Itinerary API - From-Scratch support for returnConnections
The from-scratch endpoint of the Itinerary API now supports setting the mode of transport for the return connection, i.e., the connection between the last stop in the itinerary skeleton and the end location of the itinerary. Example:
{ "startDate": "2025-08-01", "numPax": { "adults": 2, "children": 0 }, "startLocationRef": { "id": "JFK" }, "endLocationRef": { "id": "MIA" }, "legs": [ { "incomingConnection": { "transportMeans": "RentalCar" }, "stop": { "location": { "name": "New York", "countryCode": "US" }, "nights": 3 } }, { "incomingConnection": { "transportMeans": "RentalCar" }, "stop": { "location": { "name": "Miami", "countryCode": "US" }, "nights": 3 } } ], "returnConnection": { "transportMeans": "RentalCar" }, "instantiateWith": [ "rental-cars" ]}
Planner API - minor extensions
The Planner API has been extended to include the ‘carrier logo’, ‘operational carrier logo’ and ‘baggage per passenger’ attributes in the response.
.ANALYTICS
Export of Raw Data
All our TripBuilder customers with a subscription to “Advanced Analytics” have access to a new section of reports named “Advanced Analytics - Raw Data”.
This section includes reports with a simple table exposing the raw data for key model entities of TripBuilder’s analytics data and, as such, allows a CSV download of that data. The following model entities are supported: users, travel agencies, itineraries, and components. The dashboards have various filters specific to the underlying model entity.
All columns of the CSV are explained on the “Documentation” tab of the dashboard.
Remarks:
Due to the raw nature of the data, some data might show different values than those used in the Customer Care UI. For example, Itinerary Status
Multi-language fields: if available, the report always uses the English value of multi-language fields. Otherwise, the value of whichever language was available is used by the raw data tables
.FEATURES FOR UPCOMING RELEASES
Nezasa follows the “Now, Next, Later” framework to outline the development trajectory of TripBuilder, enhancing transparency around our progress. We share these insights with our customers in each new release in the TripBuilder - Now, Next, Later article.