A capability competitors cannot replicate alone
A single-carrier integration cannot return multi-operator combinations. Partners using Tictactrip ship results no DIY integration can match.
Feature · Smart combinationsWhen no direct journey exists,
When no direct journey exists,
we route across carriers
Tictactrip's routing engine assembles multi-leg itineraries from different operators — train + bus, carrier A + carrier B — when no direct service connects your user's origin and destination.
The European rail and bus network is patchy. Routing fixes that.
Direct services don't exist for most origin-destination pairs in Europe. A traveller going from a mid-sized French town to a regional Italian city typically needs two or three legs across different operators — and no single carrier's API will surface that as a bookable journey.
Tictactrip's routing engine closes the gap. We combine train and bus legs across carriers, check connection feasibility, validate fares against live inventory, and return the result as one bookable itinerary — not three separate ones for your user to assemble manually.
This is the capability that lets Tictactrip partners ship product features no competitor running a single-carrier integration can match.
- Routing engine combines train + bus legs across operators
- Multi-carrier itineraries returned as one bookable unit
- Connection feasibility validated automatically
- Cross-border combinations supported
- Useful for OTAs, MaaS platforms and corporate travel
- Falls back to direct results when they exist
Why smart combinations are a unique unlock
The capabilities partners ship on day one.
Connection logic handled for you
Transfer times, station compatibility and operational realities are validated inside the routing engine — your client never has to second-guess feasibility.
Unlock long-tail O/D pairs
Hundreds of city pairs across Europe have no direct service. Smart combinations turn those into bookable journeys instead of "no results".
Still works as a direct-search API
When a direct journey exists, you get it. The combination engine kicks in only when needed — the API surface stays the same.
Integration
One REST call, multimodal results
The same endpoint powers every Tictactrip integration. Authenticate, send a search payload, and receive itineraries with price, duration, carrier and CO₂ emissions. Then book through /book and deliver tickets to your users.
combination-search.sh
# No direct service: routing engine combines legs
curl -X POST 'https://api.tictactrip.eu/v2/results' \
-H 'Authorization: Bearer YOUR_TOKEN' \
-H 'Content-Type: application/json' \
-d '{
"originGpuid": "c|FRavignon_@spg6j",
"destinationGpuid": "c|ITmila____@u0nd6",
"outboundDate": "2026-06-12T00:00:00Z",
"passengers": [{"age": 30}]
}'Frequently asked questions
The points product and engineering teams check before integrating.
Are multi-operator itineraries bookable as one transaction?
Yes. Tictactrip handles the underlying booking sequence with each carrier and returns the combined itinerary as a single bookable record — including PNR and ticketing.
What if a leg in a combination becomes unavailable after search?
The booking endpoint re-validates each leg with its carrier. If one becomes unavailable, the booking flow returns a structured error so your platform can offer an alternative.
Does the routing engine optimise for time or price?
Each call returns multiple bundles sorted by price, with travel time and CO₂ exposed in the response. Your client decides how to rank or filter — fastest, cheapest, greenest or a custom score.
Does this support cross-border European journeys?
Yes. Cross-border multi-carrier journeys are first-class citizens — for example Paris ↔ Italian regional towns, Madrid ↔ smaller German cities, etc.
Other Tictactrip features
Ready to integrate Tictactrip?
Tell us about your project and we'll come back within one business day with a tailored plan.