Booking flows
Both booking models follow the same arc: find a train, create the booking, then pay and issue the tickets. The difference is one step in the middle. Prices are dynamic, so always create the booking against a fresh search.
Individual booking
Search trains
Call OTA_AirLowFareSearchRQ with your origin, destination, date, and passenger counts. Send one entry in originDestinationInformation for a one-way trip, or two for a round trip. Set availableFlightsOnly to false if you want sold-out classes in the results too.
If nothing matches, the response is still 200 with an empty pricedItinerary list. Treat that as no results, not as an error. A round trip is searched one leg at a time and combined, so both legs need a train.
Create the booking
Call OTA_AirBookRQ with the segment from your search, full data for up to 10 passengers, and the CTC contact. The response returns the W1 record locator, the booking’s time limits, and the cancellation penalty rules.
Pay and issue
Call OTA_AirDemandTicketRQ with the W1 locator. Payment draws from your wallet. See Paying with the wallet.
Tickets are ready
The ticketing response returns a ticket number and the amounts for each passenger, plus a download link for each ticket PDF. See Ticket documents.
Group booking
Hold the seats
Call OTA_AirPriceRQ with passenger counts by type and the CTC contact. The response returns a quoteID and the W1 record locator, which holds the seats.
Add the passengers
Add the travelers’ names and documents with OTA_AirBookModifyRQ. Do this no later than 72 hours before departure, or the booking will be invalid and dead. See Updating passengers.
Read a booking back at any time with OTA_ReadRQ and its W1 locator to check the status, the time limits, and the penalty rules. Once the booking is paid, the read response also carries the ticket numbers, the coupon status, the seat each passenger holds, and the download links.

