Continent-wide reach on day one
Hundreds of carriers, one integration. Your engineering team stops triaging carrier-specific edge cases and starts shipping product.
Feature · Multimodal coverageOne API for 250+ European
One API for 250+ European
train and bus carriers
A single REST endpoint replaces the fragmented landscape of European ground transport — no carrier-by-carrier contracts, no GDS workarounds, no parallel ticketing pipelines.
One data model for the entire European ground-transport network
European long-distance travel is split across dozens of national rail incumbents, low-cost operators and intercity bus networks. Each has its own distribution system, fare rules, identifier scheme and ticket format.
Tictactrip compresses that complexity into a single REST API. Search once and receive results from SNCF, Trenitalia, Renfe, FlixBus, BlaBlaCar Bus, ALSA, Ouigo and hundreds more — in one normalized response with consistent fields for price, duration, fare class, carrier and CO₂.
Coverage spans France, Italy, Spain, Germany, Benelux and the rest of continental Europe, including cross-border services that no single carrier exposes through its own API.
- 250+ rail and intercity bus operators
- France · Italy · Spain · Germany · Benelux · cross-border Europe
- High-speed, intercity and regional rail
- Low-cost rail (Ouigo) and high-speed (TGV, AVE, Frecciarossa)
- Long-distance bus networks (FlixBus, BlaBlaCar Bus, ALSA)
- One normalized response shape across every carrier
Why multimodal coverage matters
The capabilities partners ship on day one.
Normalized data model
Origin, destination, fare class, segments, carrier and CO₂ follow the same shape across operators. Build once and the next carrier we add ships through the same code path.
Carrier relationships maintained for you
We negotiate, certify and operate the distribution side. You see new carriers appear in your API responses rather than as new integration projects.
Cross-border itineraries
Many of the highest-margin European journeys cross borders. Tictactrip surfaces them as native results, not as second-class exception cases.
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.
search-multimodal.sh
# Multimodal search: Paris → Milan
curl -X POST 'https://api.tictactrip.eu/v2/results' \
-H 'Authorization: Bearer YOUR_TOKEN' \
-H 'Content-Type: application/json' \
-d '{
"originGpuid": "c|FRpari____@u09tu",
"destinationGpuid": "c|ITmila____@u0nd6",
"outboundDate": "2026-06-12T00:00:00Z",
"passengers": [{"age": 30}]
}'
# → mix of SNCF, Trenitalia, FlixBus and combined
# itineraries in one normalized response.Frequently asked questions
The points product and engineering teams check before integrating.
Which European carriers does the API cover?
Tictactrip aggregates 250+ rail and intercity bus operators including SNCF, Trenitalia, Renfe, FlixBus, BlaBlaCar Bus, ALSA, Ouigo, TGV, AVE, Frecciarossa and many regional carriers across France, Italy, Spain, Germany, Benelux and the rest of continental Europe.
How are different carriers normalized in the response?
Every itinerary returned by /v2/results uses the same schema: origin, destination, segments, fare class, carrier, price and CO₂. You build your UI against one model regardless of which operator serves the trip.
Can the API search cross-border journeys?
Yes. Cross-border itineraries are first-class results — Paris ↔ Brussels, Paris ↔ Milan, Madrid ↔ Lisbon, Frankfurt ↔ Amsterdam and many others.
How often is new carrier coverage added?
Tictactrip continuously adds operators. New carriers ship through the existing API surface without breaking changes — your integration picks them up automatically.
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.