Updating passengers
OTA_AirBookModifyRQ changes passenger details on an existing booking. Its main job is completing a group booking: after you hold seats with OTA_AirPriceRQ, the booking has counts but no names, and you add the names and documents here before you pay and issue. It works on individual bookings too, so you can also use it to fix a detail on a booking you made by name.
For a group, add the passengers before the updateTravellersTimeLimit, and no later than 72 hours before departure. After that the booking is dead and you cannot ticket it. See Time limits.
Reference the booking
Point the request at the booking with its record locators in airReservation.bookingReferenceID: the W1 locator and the HHR locator. Then set modificationType in airBookModifyRQ for the kind of change you are making.
Add the names
Send modificationType 3 with each traveler’s name and the segments they ride. Match travelerRefNumber.rph to the passenger slots the group booking created.
The response returns the reservation with the updated travelers. Once every passenger is in place, pay and issue.
Change other passenger details
Send modificationType 40 to change anything about a passenger except the name: gender, birth date, telephone, email, address, or the travel document. None of these affect the price. Point at the passenger with travelerRefNumber.rph and send the fields with their new values.
The response returns the traveler with the new details in airReservation.travelerInfo.
Before and after ticketing
Most changes happen before you ticket, while the booking is still open. Once the tickets are issued, what you can change narrows:
- Names are fixed. A name change with
modificationType3is refused after the tickets are issued, so get the names right before you pay. - Seats change after payment, and only then. A seat change with
modificationType5needs a paid booking, must land before theupdateTravellersTimeLimit, and cannot touch a segment that has departed or been cancelled. See Seat maps. - Every change has a deadline. Read
updateTravellersTimeLimitoff the booking and stop offering changes once it passes. Past it the API answers with code150, “Changes are not permitted”.
For the exact bodies of other modification types, the GO7 modify-booking page is the source of truth. If a change is rejected, the error response tells you why.

