Solution · Mobility & MaaS

Door-to-door travel for
MaaS & mobility platforms

Bridge your urban mobility offer to long-distance European rail and bus. One REST API, multimodal itineraries, end-to-end ticketing.

Read the API tutorial Request API access

Urban mobility is the first mile. Tictactrip is the rest of the trip.

MaaS platforms already orchestrate scooters, car-share, ride-hail, transit passes and other urban modes. What completes the experience is the long-distance leg — the train from city to city, the intercity bus across borders.

Tictactrip exposes 250+ European rail and bus carriers through a single REST API so your MaaS platform can plan, price and book the full door-to-door journey — urban mobility plus long-distance — without a second integration project.

250+ rail and bus carriers across Europe
Multi-leg, multi-operator itineraries assembled automatically
Real-time pricing and seat availability
CO₂ emissions per passenger per leg
End-to-end booking with PDF ticket delivery
Designed for MaaS routing engines and trip planners

Why Tictactrip for mobility & maas platforms

The capabilities partners ship on day one.

Long-distance layer for your MaaS

Plug intercity rail and bus into the same trip planner that already routes scooters, transit and car-share. Users get a single door-to-door itinerary instead of two disconnected apps.

Multi-operator combinations

When no direct connection exists, Tictactrip routes train + bus legs across operators into one itinerary — a key MaaS unlock for cross-border European journeys.

CO₂ per leg, ready for green routing

Every itinerary returns CO₂ emissions per passenger per leg, so your MaaS platform can offer eco-routing modes alongside fastest and cheapest.

Built to compose with other APIs

A clean REST surface, OpenAPI spec and Postman collection slot into your existing routing stack without forcing a redesign.

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.

Start the tutorial Browse the API reference

maas-search.sh

# MaaS long-distance leg: Lyon → Geneva
curl -X POST 'https://api.tictactrip.eu/v2/results' \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "originGpuid":      "c|FRlyon____@u05kq",
    "destinationGpuid": "c|CHgeneva__@u0hgq",
    "outboundDate":     "2026-06-22T00:00:00Z",
    "passengers":       [{"age": 28}]
  }'

Frequently asked questions

The points product and engineering teams check before integrating.

Can the API combine multiple operators in one journey?

Yes. The Tictactrip routing engine builds multi-leg itineraries that span several carriers when no direct service exists — a key requirement for MaaS use cases.

Is the response model compatible with MaaS routing standards?

The API returns origin, destination, departure, arrival, mode, carrier, fare and emissions per leg — the structure most MaaS routing engines expect. Our engineering team can walk through field-level mapping for your specific stack.

Does Tictactrip cover cross-border European journeys?

Yes. Coverage spans France, Italy, Spain, Germany, Benelux and most of continental Europe, including cross-border services operated by SNCF, Trenitalia, Renfe, FlixBus and many others.

How is integration handled for MaaS platforms?

We provide an OpenAPI specification, Postman collection and step-by-step tutorial. Most MaaS partners run an initial integration in 2 to 6 weeks.

Ready to integrate Tictactrip?

Tell us about your project and we'll come back within one business day with a tailored plan.

Contact sales Back to homepage