Updating passengers

Add or change passenger details on an existing booking
View as Markdown

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.

Add group passengers before the deadline

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.

modificationTypeUse it to
3Add or change a passenger name
40Change other passenger details, such as a document
5Assign seats or add special services
9Change the contact details

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.

1{
2 "version": "2.001",
3 "pos": {
4 "source": [
5 {
6 "isoCurrency": "SAR",
7 "requestorID": { "id": "AGENT001", "name": "Sample Travel", "type": "5" },
8 "bookingChannel": { "type": "OTA" }
9 }
10 ]
11 },
12 "airReservation": {
13 "bookingReferenceID": [
14 { "companyName": { "code": "W1" }, "type": "14", "id": "N6G2NW" },
15 { "companyName": { "code": "HHR" }, "type": "14", "id": "CB0255134" }
16 ]
17 },
18 "airBookModifyRQ": {
19 "modificationType": "3",
20 "travelerInfo": {
21 "airTraveler": [
22 {
23 "personName": { "givenName": ["BARAA"], "surname": "BUKHARI" },
24 "travelerRefNumber": { "rph": "1" },
25 "flightSegmentRPHs": { "flightSegmentRPH": ["1"] }
26 },
27 {
28 "personName": { "givenName": ["SARA"], "surname": "BUKHARI" },
29 "travelerRefNumber": { "rph": "2" },
30 "flightSegmentRPHs": { "flightSegmentRPH": ["1"] }
31 }
32 ]
33 }
34 }
35}

The response returns the reservation with the updated travelers. Once every passenger is in place, pay and issue.

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. You cannot change a passenger name after the tickets are issued, so get the names right before you pay.
  • Seats can still change. A seat change with modificationType 5 works after payment.

For anything else after ticketing, and for the exact seat-change body, the GO7 modify-booking page is the source of truth. Assigning seats works hand in hand with the seat map. If a change is rejected, the error response tells you why.