Traveler Modify Guide
Traveler information sent in the Add Traveler request can be added, modified, and deleted using the Traveler Updatable Items and Traveler Update requests. This topic details the workflow and payloads to modify information specifically related to travelers.
See the following topics to modify non-traveler reservation information:
- Modify remarks and service requests not sent in the Add Traveler payload
- Add ancillaries or seats
- Add an offer to a reservation with a canceled or expired offer: For GDS use Add Offer; for NDC use Standalone Reprice.
- Divide a reservation to move one or more travelers to a new reservation
- Cancel a reservation: GDS Reservation Cancel and NDC Reservation Cancel
See the following topics to modify the air itinerary on a:
- NDC held booking or ticketed itinerary: NDC Modify, Cancel, and Exchange Guide
- GDS held booking: Not supported in the JSON APIs; you must cancel and rebook
- GDS ticketed itinerary: GDS Exchanges Guide
Related Content: Booking Guide, Reservation Retrieve Guide, Traveler Updatable Items API Reference, Traveler Update API Reference
In this topic:
Traveler Data Supported Changes
The traveler-related information listed in the table below can be modified in the booking workflows as follows.
Type of data to modify
|
TravelerUpdatableItem @type value
|
Supported for: | |||
---|---|---|---|---|---|
Delete from initial booking workbench |
Delete from reservation |
Add to reservation |
Modify on reservation |
||
Frequent flyer/traveler/customer loyalty program number |
TravelerUpdatableItemCustomerLoyalty |
No |
Yes |
Yes |
Yes |
Passenger name |
TravelerUpdatableItemPersonName |
No |
No |
No for GDS Yes for NDC |
Yes |
Travel document details (passport, visa, driver license, aka SSR DOCO, DOCS, DOCA) When modifying a passport to change the passport number, note that the previous passport number is not deleted from the booking. The booking will include both the previous and updated passport numbers.
|
TravelerUpdatableItemTravelDocument |
Yes |
Yes |
Yes |
Yes |
Not currently verified for delete/add/modify for NDC.
|
TravelerUpdatableItemEmail |
Yes |
Yes |
Yes |
Yes |
Telephone Not currently verified for delete/add/modify for NDC.
|
TravelerUpdatableItemTelephone |
Yes |
Yes |
Yes |
Yes |
Address Not currently verified for delete/add/modify for NDC.
|
TravelerUpdatableItemAddress |
Yes |
Yes |
Yes |
Yes |
Name remarks Not supported for NDC.
|
TravelerUpdatableItemComments |
No |
Yes |
Yes |
Yes |
Name Changes
In the Updatable Items response, name change update status is returned in the Updatable Items response in the TravelerUpdatableItemPersonName object.
Note the following for name change support for NDC:
-
Name change allowances vary by NDC provider:
-
American Airlines (AA) allows minor changes (3 characters) to passenger first and last name or hold and ticketed orders.
-
Iberia Air Lines (IB) allows one name correction of 3 characters before check-in to either held or ticketed bookings. Not allowed if infant PTC, seats, or ancillaries associated with passenger, or ib bookings with residency discounts.
-
Qantas (QF) allows changes to a passenger's title, first name, or last name after order create and before ticketing. It can be corrected up to three characters and no fee is assessed.
-
United (UA) does not allow name changes.
-
British Airways (BA): For either a held or ticketed booking, you can change a maximum of 3 characters from the first name or title. For a held booking, you can also change up to 3 characters for the last name.
-
Qatar Airways (QR) does not support any changes to traveler information.
-
Emirates (EK) does not allow name changes on a ticketed booking. For a held booking, a maximum of 2 characters can be changed across all of the name fields in total.
-
Air France (AF) and KLM (KL) allow name changes on a held (i.e., reserved but with no payment included) and ticketed (i.e., reserved with payment included) order on AF/KL operated flights.
For non-corporate bookings, the following rules apply:
-
Change 3 letters max in the last name
-
Change full first name and/or civility
-
Modify more than 3 letters in the last name for class PF on long haul only and JCDI for all haul
For corporate bookings, the following rules apply:
-
Full name change for Corporate client in favor of an employee of the same company under contract with Air France and KLM in the following booking classes:
-
Long haul PF / JCDIZ / WSA / YBMUKHLQTEN
-
Medium haul JCDIZ / YBMPUFKHLT
-
Short haul JCIZ / WSAYBDMUPHF
-
-
-
- The carrier determines if the request is valid and follows its rules for name change. For example, a carrier might allow up to three characters to be changed in a name field. Another airline might allow an entire name change, and other carriers may not support a name change at all.
- Some name changes must be made directly with the airline.
- The carrier may need to verify the physical identification to support the name change.
- A fee may be charged for a name change.
Travel Documents (SSR DOCS, DOCO, and DOCA)
Traveler documents are added by including traveler remarks in the Add Traveler payload during the initial booking. These are converted to SSR DOCA, DOCO, and DOCS as applicable. AirReservation supports the following actions for an existing reservation:
- For GDS: Add, modify, and delete all supported DOCS, DOCO, and DOCA information on an existing reservation.
- For NDC: Add and delete only SSR DOCS P (passport). You can modify only by deleting the existing DOCS and adding a new DOCS.
- NDC carrier QR does not support any changes to traveler information.
In the Updatable Items response, travel document update status is returned in TravelerUpdatableItemTravelDocument.
Updatable Items Workflow
Specific traveler information sent in the Add Traveler payload can be modified by requesting a list of updatable items for the traveler and then sending an update request with an indicator that specifies the action to take (add, modify, or delete as applicable).
Updatable Items is supported in both the initial booking workbench and in a post-commit workbench session, however, only specific data updates are supported in each per Supported Changes above.
Step # |
Workflow Step |
Description and Notes |
API Reference |
---|---|---|---|
1 |
Create the reservation workbench |
Create either a new workbench for an initial booking or a post-commit workbench for an existing booking. Returns a system-generated identifier for the workbench that must be sent in subsequent requests for that workbench. |
|
2 |
Add Offer & Traveler (required only during initial booking) |
If an initial booking, add the offer and traveler/s, as well as any optional booking steps. |
|
3 |
Retrieve workbench (optional) |
If needed, retrieve the workbench to get the traveler ID/s. Also returned in the post-commit workbench create response. |
Retrieve Workbench API Reference |
4 |
Send Updatable Items request |
Send an Updatable Items request with the identifier for the traveler/s to update. The response returns for each traveler a list of each type of traveler information, a unique identifier for each type of information, and the indicators indicators for deletableInd, modifiableInd, and addableInd to indicate the information that can deleted, modified, or added. |
|
5 |
Send Traveler Update request/s |
Send a Traveler Update request with one or more items to update for one traveler. Include the identifier from the Updatable Items response for each item to update. Send an additional request for each additional traveler to update. |
|
6 |
Commit the workbench |
Final step in the workflow. The response returns the reservation in the same format as a reservation retrieve response, including the updated traveler information. |
Updatable Items Layout Diagram
The following diagram illustrates the general structure of the Updatable Items request and response, including most high-level objects.
Traveler Update Layout Diagram
The following diagram illustrates the general structure of the Traveler Update request and response, including most high-level objects, which follows the Updatable Items response.