Skip Navigation

SSR Codes

Some ancillaries require a SSR to be created as part of the reservation process, so that other airline departments receive notification of the ancillary sale.

The requirement to add an SSR (or not) is defined by the airline as part of the OC filing, where the airline can define if an SSR code is required, and what that SSR code should be to complete the booking of the ancillary. The SSR used to book the SSR needs to be associated to the AE.

To employ this functionality carriers need to file SSR’s associated to their ancillaries. Passengers, when presented with selected ancillaries will be instructed to supply information such as dimensions, selection of type or defined free text defined information.

Digital Connect enhances the ancillary pricing response to return the SSR codes (where applicable) and rules associated for the completion of the AE. The SSR codes are added into the AE field as part of the AE creation process.

OC/AE/EMD process manages the pricing/sale of the ancillary and ticketing, but the SSR is used to complete the reservation of the ancillary.

PNR processing would ensure that the deletion of the AE would delete the related SSR.

This functionality applies to the following flows:

  • Manage Your Booking – Change Itinerary (MYB:CI) Flow,
  • Manage Your Booking – Book Now Pay Later (MYB:BNPL) Flow.

It also gives an option to purchase a placed on hold booking that includes ancillaries with associated SSR's (in the Book Now Pay Later (BNPL) Flow). Ancillaries are held for the chosen 'on hold' option. When the passenger returns in Manage Your Booking – Book Now Pay Later (MYB:BNPL) Flow, the ancillaries and seats put 'on hold' must be purchased and no additional selections can be made.


Airlines can drive SSR for ancillaries with the following sequence of Digital Connect service calls:

  1. The passenger shops for flights and builds an itinerary.
  2. The airline calls /products/ancillaries GET to obtain list of ancillaries available for the currently selected itinerary.
  3. The airline provides SSR codes in GET /products/ancillaries. 

    The airline formats information about available ancillaries for display to the passenger.

  4. When the passenger selects ancillaries, the airline calls POST /products/ancillaries to add any ancillary products selected by the passenger to the itinerary; the information passed includes information about the SSRs.
  5. The airline can call /products GET operation to obtain a current list, with prices of products that the passenger has added to the itinerary and use this information to build and display a shopping cart.
  6. When the passenger is ready to purchase the itinerary, the airline adds field values for all applicable remarks, SSRs, and OSIs to the /purchase POST request.
  7. The airline initiates the purchase and ticketing process by calling /purchase POST ; if authorization is successful, the /purchase service will create a PNR, EMD(s), etc.
  8. The response indicates whether the purchase is successful. 

    The airline formats this information for display to the passenger.

  9. The airlines submits a /pnr GET request; the results will include remarks. 

    The airline can format the information for display to the passenger.