Skip to navigation

Update passengers on a booking

View as Markdown

Add or change passenger details on an existing booking. This is how you complete a group booking: hold the seats with OTA_AirPriceRQ, then send this request with the passengers’ names and documents before you ticket.

Reference the booking by its W1 record locator in airReservation.bookingReferenceID, and set modificationType in airBookModifyRQ:

  • 3 change or add a passenger name - 40 change other passenger details - 5 seats and special services - 9 change the contact details

Update names and documents before the updateTravellersTimeLimit, and for a group no later than 72 hours before departure. You cannot change a passenger name after the tickets are issued.

To change other passenger details, use modificationType 40: gender, birth date, telephone, email, address, or document. Point at the passenger with travelerRefNumber.rph. These changes do not affect the price.

To change a seat, use modificationType 5: put the seat in travelerInfo.specialReqDetails.seatRequests and pass the reservation you read back with OTA_ReadRQ in airReservation. Seats change only on a paid booking, before its updateTravellersTimeLimit, and never on a segment that has departed or been cancelled. Outside that window the API answers CHANGES_ARE_NOT_PERMITTED. See the examples below.

Headers

x-api-keystringRequired
local-nameenumRequiredDefaults to OTA_AirBookModifyRQ

Routes the request to the update-passengers operation.

Allowed values:

Request

This endpoint expects an object.
posobjectRequired
Point of sale. Identifies the agent and channel behind the request.
versionstringRequired
airReservationobjectRequired

The booking to change. For a name change, its record locators are enough. For a seat change, send the whole reservation you read back with OTA_ReadRQ.

airBookModifyRQobjectRequired

Response

The updated reservation.
successobjectOptional
airReservationobjectOptional
A booking as the API returns it.
versiondoubleOptional