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 help center: https://help.tripbuilder.app/en/
.PLANNER & .SMARTPLANNER
Show baggage weight allowance on flight products
Flight results previously showed "1 baggage included" without specifying the weight, which varies by airline (10 kg, 20 kg, 23 kg, etc.). Baggage weight is now displayed wherever the airline provides it.
.SMARTPLANNER
Add filters and sorting to Smart Planner flight search
Flight search results previously appeared in raw API order with no way to narrow them down. Users can now filter and sort offers to quickly find the best option for their trip. They can :
Filter by number of stops (direct, 1 stop, 2+), airline, departure time window, and maximum duration
Sort by cheapest, fastest, or best (weighted score of price, duration, and stops)
Filters and sorting combine, with a live result count and a reset option — follows the same UX pattern as hotel search filters
Display flight offers incrementally as they stream in
Flight search previously waited for all results before showing anything. Offers now appear progressively as each provider batch completes, reducing perceived wait time.
.COCKPIT
Supplier-level currency configuration for activities and ground transports
We extended the per-supplier currency configuration to ground transport and activity supply configurations. This means that if you have an activity or ground transports supplier contract in a different currency than your default sales currency, you can now specify this at the supplier level to ensure prices are displayed correctly without unwanted conversions.
When set, TripBuilder uses that currency for all requests to that supplier, ensuring consistent and correct pricing without overriding the operator's global defaults for other suppliers.
For setting the expected currency, please reach out to our Customer Support team.
.APIs
Ground Transports Connect API | Hotel details added on search requests
We added an optional hotel information field to the Ground Transports Connect API search request. When a transfer pick-up or drop-off point is a hotel, suppliers now receive the hotel's ID, name, and full street address alongside standard location data. Previously, suppliers only received a GIATA ID and coordinates, providing no hotel-specific context for suppliers that do not use GIATA, and no human-readable address for those that do.
Suppliers can now unambiguously identify hotel properties in transfer requests, enabling more accurate availability lookups and more reliable pricing, reducing the number of failed or imprecise searches caused by insufficient location context.
To learn more about this change, check our Ground Transports Connect API search request.
Booking API - Per-passenger externalRefId now exposed in booking responses
The Booking API now includes an optional externalRefId field per passenger in GET booking responses. This allows external systems to correlate TripBuilder passenger records with their own identifiers (e.g. SSIDs, CRM keys) without relying on TripBuilder's internal refId.
What's changed:
ExternalRefId is now returned per pax in the Booking API GET response
The field is documented in the Booking API OpenAPI spec under the Pax schema (paxInfo.externalRefId: string)
How to use it: Pass externalRefId per passenger when saving traveller details via the Checkout API. The value will be stored against that passenger and returned in all subsequent Booking API responses.
Note: This is distinct from the existing booking-level externalRefId. The per-passenger field allows a unique identifier per traveller, not just per booking.