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!

Nezasa's Multicenter feature transforms multi-destination travel planning by enabling travelers to create comprehensive itineraries spanning multiple cities in a single, seamless booking experience.

This new feature is now accessible via a self-service feature flag. You can opt in or out of the BETA directly from the settings, allowing you to control the visibility of the feature in your DC.

You can find more information here.

Planner users will now be notified when requested hotels have been replaced with alternatives or left unselected, improving transparency and enabling prompt review of itinerary changes.

These notifications, visible in the Planner's Notification Center, ensure further transparency and allow users to promptly review and adjust their travel plans.

We're introducing a new configuration option that enhances the hotel search experience through real-time result streaming.

What's New:
This setting enables Server-Sent Events (SSE) streaming for hotel search results, allowing search results to appear progressively as they become available from suppliers. Instead of waiting for all results to load before displaying any, users now see accommodations appear in real-time as our system retrieves them.

Key Benefits:

Configuration Path:
​

Distribution Channel Settings → Planner → Product-Specific Configurations → Accommodations → Enable Hotel Search Streaming

We have implemented the TravelGateX cheapest offer plugin to optimise hotel search performance for accommodations sourced through TravelGateX.

Changes:

Notes:

We've expanded access to SunnyCars content by removing previous rate restrictions. All configured SunnyCars users now have access to the complete range of available rate types by default, providing more options and flexibility when planning trips.

We've added a new "Sync Booking Data" action in Customer Care that allows users to manually request booking imports for API partners who need to sync booking data with mid-office systems. Previously, there was no direct way for Customer Care users to trigger a manual booking import notification, which was needed by partners consuming our API for invoicing or creating travel documentation. This was particularly problematic when adjustments were made to itineraries outside of core booking events like initial bookings, changes, or cancellations. For example, editing the net price of an inventory component or adjusting the name of a hotel.

The new feature includes a "Sync Booking Data" action available from the Customer Care Actions menu on booked itineraries only. When used, it triggers a new "Booking Sync" webhook event that API users can subscribe to receive notifications for booking import requests. The action is controlled by a feature flag and is only visible when administrators enable the "Enable Sync Booking Data action" setting.

To use this feature, administrators need to enable the "Enable Sync Booking Data action" feature flag found in DC → 3rd party integrations → Mid/back-office → General section. API users who want to receive these notifications must subscribe to the webhook event.

This enhancement enables seamless communication between Customer Care teams and API partners, allowing for more efficient booking data synchronisation with external mid-office systems for invoicing and documentation purposes.

More information here.

We've added webhook event tracking to the itinerary history section in Customer Care, providing transparency into webhook event delivery for API integrations. Previously, there was no visibility into whether webhook events were successfully sent from TripBuilder, making it difficult to troubleshoot integration issues or verify that partner systems received notifications.
​
The itinerary history timeline now includes webhook events as entries alongside other existing events. Each webhook event entry displays the date and time when the event was sent, the event type (such as BookingComplete, BookingModified, BookingCancelled), and the success or failure status from TripBuilder's perspective. This includes both automatically triggered events from normal booking operations and manually triggered events.
​
This enhancement provides Customer Care users with complete visibility into webhook event delivery, allowing them to quickly verify if events were successfully sent to API partners and troubleshoot any integration issues. The feature is generic and applies to all webhook events, not specific to any particular integration partner.

Pre-condition for Include Only rules

We've enhanced content rule management by introducing optional location-based pre-conditions for "Include Only" rules. Users can now specify geographic areas where inclusion rules should apply, providing more granular control over content distribution.

Exclusion of supplier in the Hotel Listing

An issue has been where excluded suppliers were still appearing in accommodation list views. When applying content rules to exclude a supplier from a specific source (e.g., Hotelbeds from IvectorOne), the exclusion now works correctly in both list and detail views.

User Type Consumer

We are taking the opportunity to fix a bug from the old implementation that was preventing the users to correctly exclude offers when having selected the User Type = Consumer. This fix will apply both to the New Content Rules in beta and to the old ones.

We’ve enhanced the Discovery API to include “externalReferences” at the template level, enabling better integration for clients who rely on custom product codes in their fulfillment workflows. Previously, external references were only exposed when attached to activities, limiting visibility for templates like stop-by-stop tours without activities.

With this update, external references defined in the template's “Integration” tab will now be returned in API responses, supporting seamless interoperability with external systems.

The new streaming capability communicated in the Planner section is also available for Planner API consumers.