Introduction

To support Sabre technology modernization efforts, we are changing the Sabre agency reservation logic and workflows for American Airlines (AA), which will result in AA and Sabre travel agencies no longer sharing a single reservation (PNR). This change in the booking process will affect API customers.

Currently, for Special Service Requests (SSRs) and Other Services (OSI), agencies follow separate workflows for AA and other carriers. After this change, we will begin a transitional period where both workflows will coexist; however, once the period ends, your workflows may have to be adjusted. To better understand and prepare for these potential changes in API behavior, refer to the guidelines below for the affected services.

Questions? For additional information on SSRs and other products impacted, please refer to SAN16279. If you aren't already subscribed to Sabre Advance Notifications, contact your account manager to subscribe and receive important updates.

Note: All API examples below are XML SOAP, unless stated otherwise.

Affected PNR Services APIs

Retrieve Itinerary (GetReservationRQ)

For agency PNRs created prior to activation with at least one AA flight (active/flown):

Before and after PCC activation

• All OSI/SSRs associated with AA flights are currently stored under the AFAX field.
• AA OSI/SSRs display as Type=A under GetReservationRS\Reservation\PassengerReservation\Passengers\Passenger\SpecialRequests\...

<DOCSEntry id="14" type="A"> OR <GenericSpecialRequest id="53" type="A" msgType="S">

• AA OSI/SSRs display as ssrType=AFX under GetReservationRS\ Reservation\OpenReservation\Elements\OpenReservationElement\...

<ServiceRequest actionCode="HK" airlineCode="AA" code="DOCS" serviceCount="1" serviceType="SSR" ssrType="AFX">

For agency PNRs created after activation with at least one AA flight, or agency PNRs created prior to activation that never had an AA flight (active/flown), but the AA flight was added after activation:

After PCC activation

• All OSI/SSRs associated with AA flights will be stored under the GENFAX field.
• AA OSI/SSRs display as "Type=G" under GetReservationRS\Reservation\PassengerReservation\Passengers\Passenger\SpecialRequests\...

<DOCSEntry id="14" type="G">

OR

<GenericSpecialRequest id="53" type="G" msgType="S">

• AA OSI/SSRs also display as ssrType=GFX under GetReservationRS\ Reservation\OpenReservation\Elements\OpenReservationElement\...

<ServiceRequest actionCode="HK" airlineCode="AA" code="DOCS" serviceCount="1" serviceType="SSR" ssrType="GFX">

Update Itinerary (UpdateReservationRQ)

For agency PNRs created prior to activation with at least one AA flight (active/flown):

Before and after PCC activation

To delete OSI/SSRs associated with AA flights using the optional type element:

<SpecialServiceRequestUpdate op="D" type="H">

To add OSI/SSRs associated with AA flights using the optional type element:

<SpecialServiceRequestUpdate op=”C" type="H">

For agency PNRs created after activation with at least one AA flight, or agency PNRs created prior to activation that never had an AA flight (active/flown), but the AA flight was added after activation:

After PCC activation

To delete OSI/SSRs associated with AA flights using the optional type element:

<SpecialServiceRequestUpdate op="D" type="G">

To add OSI/SSRs associated with AA flights using the optional type element:

<SpecialServiceRequestUpdate op="C" type="G">

Get Itinerary (TravelItineraryReadRQ)

Warning! This API is in the process of being decommissioned. Please migrate your application to the Retrieve Itinerary API as soon as possible.