Name Remarks

Various providers or suppliers may require additional data for a traveler on an Air segment. Name Remarks store information related to a specified traveler in BookingTraveler and BookingTravelerInfo. A name remark can be added to a passenger name in order to better identify the passenger type. For example, if an Infant passenger type is used, the name remark can include the infant's date of birth.

Providers may limit the number of Name Remarks associated to a booking traveler.

NameRemark is free-text.

A Category for each remark is also recommended, but not required. The Category attribute is stored in Universal API, but not sent to the provider, so any customer-assigned category can be added to organize types of remark data.

Many providers traditionally use Name Remarks to indicate information such as an infant's Date of Birth or the Age of a child or senior passenger, and do not use separate fields for this data. However;

• Universal API contains separate BookingTraveler Age and DOB attributes to support this content:
  • In these cases, values entered into the Universal API Age and DOBattributes may internally be converted by Universal API into Name Remarks for use by the provider's system. See the Exceptions section for further details.
  • A separate Name Remark is permitted, but not required, for this data.
• In some circumstances where Name Remarks are not supported by a supplier, an additional SSR or OSI may need to be included in the PNR to ensure that the supplier receives the traveler information.

• See the Exceptions section for provider-specific behavior.

Exceptions

Galileo

• Galileo associates name remarks to the traveler's first name. Galileo supports:

• Only one Name Remark per booking traveler. If more than one Name Remark is sent in a Universal API request, only the first Name Remark is processed, and the following warning is returned: Due to host limitation, only the first name remark could be sent.
• A maximum of 33 characters for Name Remarks. If a Name Remark is greater than 33 characters, the following warning is returned: Name Remark too long.
• Only the following special characters are supported for Name Remarks:
• Slash /
• Space
• Hyphen -
• A plus (+) sign is not supported. If a plus sign is included, the provider truncates the data beyond that plus sign.
• When an e-ticket is issued, Name Remarks are not communicated to the airline, so it is important that an appropriate SSR or OSI is added to the PNR in addition to the Name Remarks.

• Universal API sends the automatic name remark if the booking traveler is an infant. For other passenger types the name remark is not sent if not specifically mentioned in the request.

Apollo

• Apollo associates name remarks to the traveler's last name. For Apollo, the combined length of the traveler's name and associated Name Remarks cannot exceed 55 characters.

• Only the following special characters are supported for Name Remarks:

  • Slash /
  • Space
  • Hyphen
• A plus (+) sign is not supported. If a plus sign is included, the provider truncates the data beyond that plus sign.
• When an e-ticket is issued, Name Remarks are not communicated to the airline, so it is important that an appropriate SSR or OSI is added to the PNR in addition to the Name Remarks.

• Universal API sends the automatic name remark if the booking traveler is an infant. For other passenger types the name remark is not sent if not specifically mentioned in the request.

Worldspan

• For child and infant travelers, an additional SSR is required.

• Universal API sends an automatic name remark irrespective of the passenger code.

ACH

ACH requires the date of birth for CHD and INF passenger types, which is passed in the Name Remarks field.

Because ACH suppliers do not consistently return Booking Traveler information in the response, any relevant data is taken from request and included in the response. However, the response data is not synchronized with the supplier.

RCS

RCS does not support Name Remarks.