Train API
Add rail to your travel platform — search trains, validate fares, book and cancel through one normalized API.
8
documented endpoints
Validated
fares before booking
Full
booking lifecycle
1 envelope
normalized JSON
What the Train API gives you
One integration, one JSON envelope — the same credentials you use for flights and hotels.
Train search
Search available train journeys for a route and date.
Single train details
Open one train for its full schedule and fare information.
Fare validation
Validate the train and fare before booking, and read the validated details by tracking ID.
Traveller details
Add traveller information to the validated journey.
Book, retrieve and cancel
Create the booking, retrieve booking details and cancel over the API.
Rail next to air
Same integration as flights, so rail and air options can sit side by side in your search.
Booking flow
8 documented endpoints, called in this order. Every call is a POST to the base URL issued with your credentials, and returns a tracking_id you carry into the next step.
- 1Train search — search available train journeys
- 2Single train — get details for a specific train
- 3Validate — validate train selection and fare
- 4Validation details — read validation details by tracking ID
- 5Update traveller — add traveller information
- 6Create booking — confirm the train booking
- 7Booking details — retrieve the booking
- 8Cancel booking — cancel a train booking
Full request and response fields are in the API documentation.
Response envelope (abbreviated)
Shape follows the shared Tripgic envelope; product-specific fields are listed in the documentation.
Explore more inventory
Frequently asked questions
What does the Train API cover?
Searching train journeys, viewing a single train, validating the fare, adding traveller details, booking, retrieving and cancelling — eight documented endpoints.
Is the fare confirmed before booking?
Yes. The validate step confirms the train and fare, and the validation details can be read back by tracking ID before you create the booking.
Can bookings be cancelled?
Yes. The Train API includes a cancel booking endpoint.
Does it use the same format as the other Tripgic APIs?
Yes. It uses the same authentication and the same JSON envelope — status, message and a tracking_id — as every other Tripgic API, so your existing integration patterns carry over.
Which plans include the Train API?
The Train API is available on request. Book a kick-off call and the team will add it to your plan.
Ready to add rail to your platform?
Book a short kick-off call, get sandbox credentials at no charge, and build against the same schema you'll use in production.