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 Orchestrated Sabre APIs

• Passenger Details
• Create Passenger Name Record | SOAP | REST
• Update Passenger Name Record | SOAP | REST

Before PCC Activation

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

When adding an OSI/SRR associated with an AA flight, and the optional <VendorPrefs> node is used, enter the following:

JSON:

XML:

Notes:

• When <VendorPrefs> is not specified, the Action Codes 3 or 4 are automatically orchestrated by the API.
• Refer to the Create PNR v2.4.0 WITH Optional Vendor Preferences and Create PNR v2.4.0 NO Vendor Preferences code samples to see how this is applied.

Important! 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 had an AA flight added after activation, there is no change.

After PCC Activation

Scope

• For agency PNRs created prior to activation with at least one AA flight (active/flown).
• 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 had an AA flight added after activation.

When adding an OSI/SRR associated with an AA flight, and the optional <VendorPrefs> node is used, enter the following:

JSON:

XML:

Notes:

• When <VendorPrefs> is not specified, the Action Codes 3 or 4 are automatically orchestrated by the API.
• Refer to the Create PNR v2.4.0 WITH Optional Vendor Preferences and Create PNR v2.4.0 NO Vendor Preferences code samples to see how this is applied.

Recommendations