The following workflow is used to display a seat map with prices for a given carrier code, flight number, class of service, board point, off point, and departure date.
Information returned in the EnhancedSeatMapRS contains the seat map data and the exact prices for each paid seat, in addition to a seat map banner. Seat map data includes specific seat characteristics (e.g., aisle, window), cabin facilities description (e.g., bar), as well as a list of available amenities (e.g., pillow). If chargeable seats are present in an aircraft, specific seat prices are included in the response. Depending on the seat prices found in the seat map data, the seat map banner includes either one standard price for all paid seats, two prices (standard and premium), or a price range (if there are more than two seat pricings in the aircraft). Each seat that is marked as chargeable on the seat map should have a price. If the price cannot be determined for a seat that is marked as chargeable, the seat is flagged as "General Restricted" on the map to prevent users from requesting the seat for free.
This workflow requires the client application to have an air segment booked.
The air segment should be booked for a given passenger if seat map prices are to be passenger-specific.
Step 1: Shop one or more flight segments (for instance using Low Fare Search and Book).
Step 2: Book one or more flight segments (for instance using EnhancedAirBookRQ).
This API can also be used to request additional information about rules, flight details, and seating, including upselling to other options.
Step 3 Optional: Collect passenger-related data (e.g., passenger name, passenger type, Frequent Traveler etc.). If seat map information is to be passenger-specific, passenger data needs to be provided.
Step 4 Optional: Add all required information to create a passenger name record (PNR) and end transaction (for instance using PassengerDetailsRQ).
Note: If the client application requires additional functions to be executed for a given transaction, please navigate to Sabre Dev Studio to review available Sabre APIs details.