Skip to navigation

Booking models

Book by name, or hold seats and add names later
View as Markdown

There are two ways to create a booking. Which one you use comes down to a single question: do you already have the passengers’ names?

Individual booking

Use OTA_AirBookRQ when you know who is traveling. Send full passenger data for up to 10 travelers in one booking. Each traveler needs a name, a document, and the segments they ride. You also send one CTC contact passenger for the booking.

The response returns the W1 record locator and the booking’s time limits. From here you pay and issue the tickets.

Group booking

Use OTA_AirPriceRQ when the names are not ready yet. Send passenger counts by type instead of names, plus one CTC contact passenger. The response returns a quoteID and the W1 record locator, which holds the seats.

Add the passengers and issue the tickets no later than 72 hours before departure. This deadline is tied to the train, not to when you created the booking. Book weeks ahead and you still have until 72 hours before it leaves. Miss the deadline and the booking is released. See Time limits for the full set of deadlines.

The CTC contact passenger

Both models require a CTC contact passenger. This is the person the railway contacts about the booking, and it carries the email that receives the tickets and any cancellation notice. The CTC passenger is separate from the travelers and does not take a seat.

What every booking needs

Both requests share the same frame: version 2.001, a pos block that names your agent and agency with bookingChannel.type OTA, and the airItinerary segment copied from your search. The passenger part is where they differ.

BookingPassenger data
Individual (OTA_AirBookRQ)travelerInfo.airTraveler: one CTC contact, then each traveler with passengerTypeCode, personName, gender, and a document.
Group (OTA_AirPriceRQ)travelerInfoSummary.airTravelerAvail: passengerTypeQuantity counts for ADT, CHD, and INF, plus one CTC contact.

Every traveler except the CTC contact needs a complete document:

FieldWhat to send
docIDPassport or national ID number.
docType2 for a passport, 5 for a national ID.
docHolderNationalityISO country code, such as SA.
birthDateThe traveler’s birth date as YYYY-MM-DD.
expireDateThe document’s expiry date as YYYY-MM-DD.
"document": [
{
"docID": "1234567890",
"docType": "5",
"docHolderNationality": "SA",
"birthDate": "1990-01-01",
"expireDate": "2030-12-31"
}
]

Email and telephone are optional on every traveler, including the contact. The contact’s email is where the tickets go, so always fill it in.

What the booking returns

Both responses return the W1 record locator. They also carry the fare rules for each segment under fareInfos.fareInfo[].ruleInfo: the booking’s deadlines in tpaextensions, and the cancellation penalty windows in chargesRules. Read the deadlines in Time limits and the penalties in Cancelling. A segment that has been cancelled carries no rule information.

Which one to reach for

Individual booking

Names known. Up to 10 passengers. Full data up front with OTA_AirBookRQ.

Group booking

Names not ready. Hold seats with counts using OTA_AirPriceRQ, then add names before the 72-hour deadline.