Booking Traveler Name

The BookingTravelerName defines a traveler's name. Additional information related to the traveler can be included in Name Remarks.

 

First and last names are required. Middle names, prefixes, suffixes are optional. All attributes are text strings.

Traveler Name Limitations

The following limitations for traveler names on reservations should be considered when designing input parameters for client applications.

Valid Characters

Only Latin characters are allowed as part of the name. Special characters such as á, ū, ß, Æ, Ø, etc. are not allowed.

Note: Because these characters are not allowed, here are tips on how to spell these names:

Length of Name

The length of entire name, including prefix, first name, middle name, last name, spaces, and suffix, cannot exceed:

Notes:

Numbers in Names

While numbers are allowed to be contained within a name, neither the first name nor the last name can consist entirely of numbers.

For example, attempting to add travelers with any of the following names to the reservation will result in an INVALID_INPUT_DATA exception:

Name Space

Schemas for Air, Hotel, Vehicle, and Universal, v48.0 and greater, allows spaces in name field in Galileo to align with other GDSs, for Air, Vehicle, and Hotel services, so that name is consistent with traveler ID, frequent flyer ID, etc. Release 21.1

Previously, in Galileo (1G), in UniversalRecord/BookingTraveler/BookingTravelerName, you could include spaces in the name, but all spaces were stripped out when sent to the GDS, so that the name in the Galileo PNR did not have spaces. Additionally, any extraneous beginning or ending spaces were stripped out when saving to the Universal Record; middle spaces remained.

The name entered in the request is saved to the Universal Record, including beginning, middle, or ending spaces. The name entered in the request is sent to the Galileo PNR.

To add a space between the first name and the title (MR/MRS),

Copy 
Prefix=" MR"
<com:BookingTravelerName Prefix=" MR" 
Last="CHOPRA" First="ROHIT" />
Copy 
First="ROHIT "
<com:BookingTravelerName Prefix="MR" 
Last="CHOPRA" First="ROHIT " />

Name Uniqueness

When creating a reservation, the traveler name is stored exactly as it was entered; this name displays when the reservation is viewed or otherwise manipulated. However, to be compatible with other computer systems, all traveler names are reduced to simple firstname-lastname pairs.

This reduction leads to problems when it is necessary to accommodate similar names on the same reservation. For example: Mr. John James Smith Sr. and Mr. John James Smith Jr.

To reduce names to firstname-lastname pairs while still retaining as much uniqueness as possible, the following method is applied:

Thus, Mr. John James Smith Sr. becomes JOHNJAMESMRSR SMITH, and Mr. John James Smith Jr. becomes JOHNJAMESMRJR SMITH. This solution keeps both names unique while reducing them each name to the necessary simple pair.

While this method solves uniqueness problems for the overwhelming majority of names (e.g., those differing only by prefix, suffix and/or middle name), it can, under rare conditions, cause confusion. In general, the method used to create the name pair described above can also result in rejection of multiple traveler names which originally appear unique.

For example, the following sets of names are NOT allowed on the same reservation because they resolve to the same firstname-lastname pair:

Exceptions

ACH

Jet2 (LS) also requires the traveler's gender in the booking request. Universal API maps the gender based on the name prefix. Uncertain prefixes are mapped to Male.

RCS