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!

When an inventory hotel booking includes a special offer, the ‘name’ of that offer will now be automatically included in the emails sent to the local supplier. This ensures that hotels are immediately aware of any special conditions or promotions applied to the booking.
​
The booking confirmation, change, and cancellation emails for inventory hotels have been updated to clearly display the name of the special offer. This provides better clarity and avoids potential confusion regarding the booking details.
​
Note that initially, the name of the special offer, where the special offer type is a child reduction, is not yet displayed in the emails sent to the local supplier. This scenario will be covered in a future follow-up.

In a few weeks, we’ll release improved P2P support where content sources will become part of the supply reselling rules, and stored on connected supply reselling rules per product type. This will ensure that the module owner, or seller, can control exactly which content sources are used in the modules they are selling to a reseller. From the reseller perspective, this will ensure that they will only source the content defined by the module owner.
​
In preparation of this, we have started the configuration of the feature in settings. An in-app message has been configured for the new content sources section within the reselling rules. This message will display the text: "Feature in development. Do not use.", until developments are completed.

A tax and fee disclaimer will now be included in the pricing section of the Travel Document when an Expedia offer is part of the booking.

The disclaimer text will read: "The taxes are tax recovery charges paid to vendors (e.g., hotels); for details, please see our Terms of Use. Service fees are retained as compensation in servicing your booking and may include fees charged by vendors."
​
This ensures transparency regarding taxes and fees for Expedia-sourced components.

The Booking API has been updated to allow API users to easily identify which ticket belongs to each passenger.
​
The Booking API response has been enhanced to include information at the included.attributes.legs.segments. This means that if ticket details were present, the API now provides, for each segment, a 'tickets' attribute which displays both the passenger ID and relevant ticket number.
​
We have deprecated the original ‘ticketinformation’ attribute, given the new improvements that give more granular detail on the segment level.

GIATA IDs for accommodation components will now be included in the external reference attribute of the Booking API response under the following conditions:

This ensures that GIATA IDs are provided when they are relevant and have been explicitly requested by the customer with a valid GIATA contract.

We have enhanced the Booking API to include information on foreign exchange (FX) conversion, for the components and their amenities where currency conversion has occurred. The FX rate information will be located on the sales price of the component and its amenities. This information will be available in the API response for the current itinerary as well as in the booking history. The following details will be included: the original currency of the sales price and the exchange rate applied to convert the amount from the original currency to the displayed currency.
​
FX conversion information will only be included when the original currency differs from the main currency of the itinerary. This enhancement provides greater transparency regarding pricing and currency conversions.
​
​Note for Marketplace Operators: If the component was sourced from the Marketplace and a currency conversion occurred between the supplier's selling currency and the Marketplace Operator's sales currency, the ‘pricewithoutmarkup’ of the first markup entry in the component details will now include FX conversion information. This will include the original currency and the exchange rate applied. This applies when the requesting user is not a reseller.

The Checkout API has been updated to make the age field optional, removing the default value of 0 that previously caused ambiguity between adults and newborns. Now, if the age is not explicitly set, it will be assumed that the passenger is an adult, because child and infant ages are always defined. Additionally, once a birthdate is provided, the age will reflect the traveller's age at the itinerary's start date, ensuring clarity and accuracy in age-related data.

We are pleased to announce enhancements to our Connect API for accommodations, catering for more detailed and comprehensive room-level information. This update allows our suppliers to share enriched data, enhancing the overall user experience.

Suppliers can now share detailed room information, including:

These enhancements are available only if supported by the third-party sources which is integrated via the Connect API for accommodations.

The content, when available by the supplier source, will also be retrievable by Planner API consumers.

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.