Skip to main content

Travel Agency and AA PNRs

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

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:

"VendorPrefs": {
    "Airline": {
        "Hosted": true

XML:

<VendorPrefs>
    <Airline Hosted="true" />
</VendorPrefs>

Notes:

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:

"VendorPrefs": {
    "Airline": {
        "Hosted": true

XML:

<VendorPrefs>
    <Airline Hosted="true" />
</VendorPrefs>

Notes:

Recommendations

Ideal Basic
Upgrade (if applicable) to the latest API version and remove the <VendorPrefs> node altogether. Since the Sabre system orchestrates the storage of all AA OSI/SSRs under the General Fact field, no changes are required in the way these APIs are consumed.