Standalone Seat Map API Reference

POST	search/seat/catalogofferingsancillaries/seatavailabilities Base path: Pre-production https://api.pp.travelport.com/11/air/ Production https://api.travelport.com/11/air/

Related Content: Seats Guide, Seat Book API Reference

Standalone Seat Map sends flight criteria including a booking A confirmed reservation with the carrier. A held booking is a reservation that has not yet been ticketed. The terms booking and reservation are interchangeable. code to return a view-only seat map. Unlike the Seat Map request, Standalone Seat Map does not send any identifiers from a previously searched or priced flight. It is instead a full payload In the JSON APIs, an API call that sends all details of the flight/s to be shopped, priced, added to the workbench, etc. instead of sending a reference to an offer in a previous API response. request and can be sent entirely on its own, either within or outside of a workbench session.

To subsequently select a seat, you must send a Seat Book request in a workbench session to add the selected seat/s to the workbench.

GDS

Global Distribution System. A GDS aggregates and distributes air, hotel, and car rental content such as schedules, fares, and upsells. In the JSON APIs, GDS content is distributed from Travelport. only; not supported for NDC

New Distribution Capability, an XML standard for exchanging data that supports airlines in distributing their content directly to online travel agencies. See the NDC Guide..

Request

Also see Authorization and Common Headers.

Query Parameters

None.

Request Body

Show Standalone Seat Map Request Body Table

Object	Description	Required/Optional
CatalogOfferingsQuerySeatAvailability	Top level object.	Required
SeatAvailabilityOfferings	Top level object. Send with @type value SeatAvailabilityOfferingsBuildFromProducts.	Required
ProductCriteriaAir	Top level object for itinerary The entire trip on a booking, including all flights on all legs. Also called a journey. details. Includes SpecificFlightCriteria.	Required
SpecificFlightCriteria	Array. Each instance sends details for one segment A flight or flights under one flight number. One flight equals one segment. A segment could have multiple flights if the flight number remains the same, which happens if a flight makes a stop without changing planes. (aka flight) to return seats.	Required
carrier An airline.	String. IATA International Air Transportation Association, an organization that standardizes rules, regulations and fare construction principles for the international travel industry. code of airline carrier for flight.	Required
flightNumber	String. Flight number assigned by airline.	Required
departureDate	String. Departure date of flight in YYYY-MM-DD format (e.g., departureDate="2024-12-06")	Required
departureTime	String. Departure time of flight. HH:MM:SS (24-hour) format (e.g., departureTime="18:00").	Required
arrivalDate	String. Arrival date of flight in YYYY-MM-DD format.	Required
arrivalTime	String. Arrival time of flight in HH:MM:SS (24-hour) format.	Required
from	String. IATA airport code of departure.	Required
to	String. IATA airport code of arrival.	Required
cabin	String. Cabin class to return seats for. If neither cabin, classOfService, or additionalCabins are sent, by default the response returns Economy cabin and Y class of service.	Optional
classOfService	String. Class of service to return seats for.	Optional
segmentSequence	Sequence of this segment on the leg The flight or connecting flights between one origin and destination pair. For example, on a round-trip flight, LAX > MSP could be the first leg (aka outbound leg) and MSP > DEN > LAX could be the second leg (aka inbound leg). The JSON APIs use the term product (see below) to represent one leg of the itinerary., starting with 0 for the first segment on the leg. A segment is one flight with the same flight number.	Required

Response

The Standalone Seat map response is the same as the reference payload In the JSON APIs, an API call that sends identifers referring to a previous response for the itinerary to be shopped, priced, added, etc. instead of full itinerary details. seat map response, with the exception that Result/Warning/Message is returned with the message The seatMap is view only. See the Seat Map API Reference for response details.

Example Request

For additional examples and scenarios, download the developer toolkits and see Using Postman and Developer Toolkits.

Show Example

{
 "CatalogOfferingsQuerySeatAvailability": {
  "SeatAvailabilityOfferings": {
   "@type": "SeatAvailabilityOfferingsBuildFromProducts",
   "ProductCriteriaAir": {
    "@type": "ProductCriteriaAir",
    "sequence": 1,
    "SpecificFlightCriteria": [
     {
      "@type": "SpecificFlightCriteria",
      "carrier": "QF",
      "flightNumber": "940",
      "departureDate": "2024-06-30",
      "departureTime": "17:35:00",
      "arrivalDate": "2024-06-30",
      "arrivalTime": "23:55:00",
      "from": "PER",
      "to": "BNE",
      "cabin": "Economy",
      "classOfService": "Q",
      "brandTier": 2,
      "segmentSequence": 1,
      "AvailabilitySourceCode": "Z",
      "ContentSource": "GDS",
      "boundFlightsInd": true
     }
    ]
   }
  }
 }
}

Example Response

The Standalone Seat map response is the same as the reference payload seat map response, with the exception that a Result/Warning/Message is returned with the message The seatMap is view only. See the Seat Map API Reference for an example response.