OpenAPI-first
Every endpoint is described in OpenAPI 3, with request and response schemas. Generate clients in your language of choice or wire it straight into your existing codegen pipeline.
Feature · Developer-firstA multimodal travel API,
A multimodal travel API,
built for engineers
Clean REST endpoints, an OpenAPI specification, a ready-to-use Postman collection and a step-by-step tutorial. Prototype on day one, ship in weeks.
Most travel APIs treat developers as an afterthought. We don't.
European ground-transport distribution is historically dominated by SOAP integrations, ZIP-file ticket layouts and PDF documentation. Building on top of it has been a multi-quarter slog for every team that tried.
Tictactrip ships the opposite of that. A clean REST API, a complete OpenAPI specification, a Postman collection you can import in one click, curl examples in every tutorial step, and an interactive API reference where every endpoint is documented with request/response schemas.
Most engineering teams prototype on day one and ship a production integration in 2 to 6 weeks.
- Pure REST API — no SOAP, no proprietary SDK lock-in
- OpenAPI 3 specification covering every endpoint
- Ready-to-use Postman collection
- Curl examples for every step of the booking flow
- Interactive API reference (Redocusaurus-powered)
- Typical integration time: 2 to 6 weeks
Why a developer-first API matters
The capabilities partners ship on day one.
Prototype on day one
Import the Postman collection, paste your authentication token, and you are hitting live search results inside five minutes. No multi-week onboarding before you can write code.
Tutorials, not just reference docs
A step-by-step tutorial walks through search, reservation, payment, ticketing, refunds and exchanges with curl examples — the kind of content that turns a reference doc into a shippable integration.
2 to 6 weeks to production
Most partners go from "first curl" to "production traffic" in 2 to 6 weeks. We work directly with your engineering team to unblock anything that gets in the way.
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.
first-call.sh
# Your first call: paste, replace the token, run.
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|FRlyon____@u05kq",
"outboundDate": "2026-06-12T00:00:00Z",
"passengers": [{"age": 30}]
}'Frequently asked questions
The points product and engineering teams check before integrating.
Is the API REST?
Yes — clean REST endpoints, JSON request and response bodies, standard HTTP status codes. No SOAP, no proprietary SDK requirements.
Do you provide an OpenAPI specification?
Yes. The full OpenAPI 3 specification is published at developers.tictactrip.eu/api and used to render our interactive API reference.
Is there a Postman collection?
Yes. A ready-to-use Postman collection is linked from the tutorial — import it, paste your authentication token and you are running real searches in minutes.
How long does a typical integration take?
Most partners go live in 2 to 6 weeks. The exact timeline depends on the scope of your integration (search-only vs full booking) and the number of carriers you need.
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.