No stale data
Every search returns prices and availability that are live with the carrier — what your user sees is what they can actually book.
Feature · Real-time availabilityLive pricing & seat availability,
Live pricing & seat availability,
refreshed on every search
Every Tictactrip search hits live carrier inventory. Prices, fare classes and seat availability are current at the moment the user clicks — no caching, no stale data, no failed bookings.
Stale inventory is the leading cause of broken travel bookings
Travel platforms that cache fares end up the same place: showing a price that no longer exists, then dropping the user into an error flow at checkout. The fix is structural — every request must reach live carrier inventory.
Tictactrip proxies directly to carrier systems on every call. Prices, seat availability and fare classes returned by /v2/results are the prices your user can actually book in the next few seconds.
For partners, this means lower conversion drop-off, fewer support tickets and no manual reconciliation between displayed and charged fares.
- Live carrier-side pricing on every request
- Real-time seat availability and fare classes
- No stale-cache mismatches at checkout
- Coverage across 250+ European rail and bus operators
- Sub-second responses for the most common routes
- Returns the exact bookable fare, not an estimate
Why real-time availability matters
The capabilities partners ship on day one.
Higher checkout conversion
The number-one driver of cart abandonment in travel is "price changed at checkout". Tictactrip eliminates the gap between display and book.
Fare-class accuracy
Refundability, advance-purchase windows and fare-class metadata are returned in the same response, so policy and pricing logic stay in sync.
Latency tuned for in-app UX
Sub-second responses on the most common European routes mean Tictactrip slots into the search-as-you-type and instant-results flows your users expect.
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.
realtime-search.sh
# Live search: every call hits carrier inventory
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.
Does Tictactrip cache fare data?
No. Every call to /v2/results hits live carrier inventory. The fares and availability you see are the ones your user can book immediately.
What latency should I expect?
Most European rail and bus routes return in well under a second. Some long multi-leg multi-operator searches take longer because they hit several carrier systems in parallel.
What happens if a fare changes between search and book?
The booking endpoint re-validates fare and availability with the carrier. If the price has moved, the booking step returns the current fare instead of silently charging a different amount.
Can I prefetch or batch searches?
We work with high-volume partners to optimise traffic patterns. Pre-fetching popular routes is supported on certain plans — contact sales@tictactrip.eu to discuss.
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.