No parallel ticketing stack
You integrate one booking flow instead of carrier-by-carrier ticket-issuance logic. The maintenance burden of ticket formats lives on our side.
Feature · End-to-end bookingSearch, reserve, pay, ticket —
Search, reserve, pay, ticket —
through one REST API
Tictactrip handles the entire booking pipeline. Tickets come back as PDFs, ready to email to travellers or render inside your own product. Refunds and exchanges run through the same surface.
The booking pipeline is the part nobody wants to rebuild
Search is the easy 20% of a travel integration. The other 80% is reservation locks, payment authorization, carrier-specific ticket issuance, retries, refunds, exchanges and after-sales operations — the unglamorous infrastructure that decides whether your product works in production.
Tictactrip owns that pipeline end-to-end. You hit one REST API; we run the booking sequence against each carrier, validate payment, issue the ticket and return it as a PDF you can email to travellers or embed inside your own app.
Refunds and exchanges run through the same API. No carrier portals, no manual reissues, no parallel ticketing stacks.
- Search → reserve → pay → ticket through one REST API
- PDF ticket delivery, ready to email or embed
- Refund workflows through the same API surface
- Exchange and modification workflows supported
- Carrier-side reconciliation handled by Tictactrip
- Consistent booking record format across operators
Why one API for the entire booking flow
The capabilities partners ship on day one.
Payment-clean workflow
Reservation, payment and ticket issuance happen in a structured sequence with clear error codes — easy to wrap in your own retry and observability stack.
Refunds and exchanges included
Cancellation and modification workflows run through the same API. No need to point your support agents at five different carrier portals.
PDF tickets, ready to send
Tickets are delivered as PDFs your platform can email, attach to confirmations, store in a document system or render inside your own product.
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.
booking-flow.sh
# Step 1 — search for itineraries
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}]
}'
# Step 2 — reserve, pay and issue tickets
# using the booking endpoints in /docs/introFrequently asked questions
The points product and engineering teams check before integrating.
In which format are tickets delivered?
Tickets are issued as PDFs. You can email them to travellers, attach them to confirmation emails, archive them in a document system or render them directly inside your own product.
How are refunds handled?
Refund workflows run through the same API. Eligibility, partial vs full refund and timing follow the original carrier fare rules — surfaced through structured API fields, not free-form text.
Are exchanges supported?
Yes, where the carrier supports them. The exchange endpoint runs through the same API surface as the original booking — your platform handles the user-facing flow, Tictactrip handles the carrier-side mechanics.
What happens if a payment fails mid-booking?
The booking endpoint returns structured error codes so your platform can decide whether to retry, fall back to another itinerary or surface the failure to the user. No silent partial bookings.
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.