Skip Navigation

SSR Codes

The service that obtains information about seats that are available for any flights that the passenger has selected and populates a seatmap for the passenger has the following additions and enhancements:

Consistent and easy to identify a way of showing various seat cost.

Seat map will be able to display seat prices with price tiers, by attributes and with consistent coloring.

The seat map request can pass any promo code SSRs supplied by the passengers as query parameters; these will be used in seat price calculations.

The seat pricing responses will return required SSR codes (where applicable) as part of the seat price list response in the Post Booking flows.

The airlines will define the required SSR codes as part of the OC fare record. The SSR code and associated information will be added into the AE field as part of the AE creation process.

The seat map response will return available seating and pricing per passenger with any discounts or waivers applied based upon entitlements provided in the downline systems. The entitlements may be based on passenger’s frequent flyer tier, any applicable deals defined in the downline systems (i.e. passenger purchased an ancillary bundle that includes a seat), and any SSRs that have been specified by the passenger.


The /products/seats request generates a response that takes into account any entitlements that are determined to be applicable to the passengers. Seat entitlements can include:

  • Fee waivers or discounts applied to seat prices, for the primary passenger and/or travelling companions,
  • Specific seats becoming available to the primary passenger and/or travelling companions.

Entitlements can be based on:

  • Dynamic retailer discount programs,
  • Passenger’s frequent flyer tier level, as determined by the passenger’s profile information,
  • Promotional codes passed with the request.

An example flow of the services for the Manage Your Booking – Change Itinerary (MYB:CI) Flow:

  1. The passenger retrieves a booking either by supplying basic PNR information or by logging in to a Frequent Flyer account. If the passenger is logged in, all their reservations are visible. Airlines can prompt passengers for information that identifies a PNR, retrieve the information and format it to display to the passenger.
  2. The /pnr/exchange service GET operation returns information for the PNR specified in the parameters and initializes Exchange process.
  3. The Airline obtains search criteria from the passenger and submits a /pnr/exchange/products/air/search request, POST operation to get a list of flights matching the search criteria. Display the returned flights to the passenger.
  4. After the passenger selects one or more flights, the Airline submits the /pnr/exchange/products/air POST operation to add the flights to the itinerary and store the itinerary in the session.
  5. The Airline calls /pnr/exchange/products/seats GET to obtain seat map for the currently selected itinerary.
  6. The Airline provides also SSR codes (promoSSRs) in GET /pnr/exchange/products/seats to obtain possible discounts for seats (possible discounts are based on different factors, like tier level).
  7. When the passenger selects seats, the Airline calls POST /pnr/exchange/products/seats to add seats selected by the passenger to the itinerary.
  8. The Airline can call /pnr/exchange/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. The response for the ancillaries and seats will include a breakdown of the original amount, discount and discount amount
  9. When the passenger is ready to purchase the itinerary, the Airline adds field values for all applicable remarks, SSRs, and OSIs to the /pn/exchange/purchase POST request.
  10. The Airline initiates the purchase and ticketing process by calling /pnr/exchange/purchase POST; if authorization is successful, the /purchase service will create a PNR, EMD(s), etc. EMDs will be issued with discounted values.
  11. The response indicates whether the purchase is successful.
    The Airline formats this information for display to the passenger.
  12. The Airline submits a /pnr/exchange GET request; the results include remarks.
    The Airline can format the information for display to the passenger.