<Document>
<Success>
<ALaCarteOffer>
<SeatMap>
<DataLists>
User Guidance | |||||||
Input Parameters | Type | Mandatory/Optional | |||||
Request Object | SeatAvailabilityRS | M | |||||
< SeatAvailabilityRS > | |||||||
XML Example for the following elements
| |||||||
Elements | Details | Mandatory/Optional | |||||
Version (Attribute) | Specify NDC schema message version. Always pass 17.2 Note: This is a mandatory attribute in NDC schema. The service will not validate what is being passed in this attribute | M | |||||
<Document> | |||||||
XML Example for the following elements
| |||||||
Elements | Details | Mandatory/Optional | |||||
Document | NDC Message Document information | M | |||||
Name | Document name will be always "NDC | O | |||||
ReferenceVersion | It will be NDC version | O | |||||
<Success> | |||||||
Elements | Details | Mandatory/Optional | |||||
Success | The presence of the empty Success element explicitly indicates that the message succeeded | M | |||||
<Processing> | |||||||
Elements | Details | Mandatory/Optional | |||||
Processing | Message Processing Results. May include errors, business warnings, alternate offers indicator, supplemental marketing messages and/ or additional information required to complete a transaction. | O | |||||
<ALaCarteOffer> | |||||||
Elements | Details | Mandatory/Optional | |||||
ALaCarteOffer | Container for standalone optional OfferItems. | M | |||||
| |||||||
OfferID (Attribute) | Airline-assigned unique Offer identifier. | M | |||||
Owner (Attribute) | Airline designator of the owner/ assigner of the Offer ID. Example : BA, XQ, EK | M | |||||
XML Example for the following elements
| |||||||
ALaCarteOfferItem | One Service or Service Bundle which is priced per unit. | M | |||||
OfferItemID (Attribute) | Unique identifier for this OfferItem instance. | M | |||||
Eligibility | Refers to the Passengers, Price class or Segments for which this offer item is eligible | M | |||||
PassengerRefs | Reference to the passengers who are eligible for this Offer Item | M | |||||
SegmentRefs | Segment Reference | M | |||||
UnitPriceDetail | Flat price for an individual unit of the referenced Service | M | |||||
TotalAmount | Total price amount. | M | |||||
DetailCurrencyPrice | A (detailed) CURRENCY-based Price with Price Break-down. | M | |||||
Total | Total seat price | M | |||||
Code (Attribute) | Currency code | M | |||||
Service | One or more instances of a service definition (as found in DataLists) as it has been offered, and eventually ordered and consumed by a specific Passenger in the context of an Offer. | M | |||||
ServiceID (Attribute) | Unique id for a service Example: V1_SRVC.1560995779189 | M | |||||
ServiceDefinitionRef | Reference to ServiceItems across different OfferItems | M | |||||
<SeatMap> | |||||||
SeatMap | This element shows the seat map of a particular segment. Returns a list of cabins and the seats within it.
| M | |||||
Cabin | This is a list and will be repeated once for upper deck and once for the main deck when the requested cabin is spread across the upper and main deck.
| M | |||||
UpperDeckInd (Attribute) | “True” means this seat is on the upper deck | O | |||||
<CabinType> | |||||||
CabinType | Cabin type. Example : ECONOMY, BUSINESS | M | |||||
XML Example for the following elements
| |||||||
Name | ECONOMY | O | |||||
Code | Y | M | |||||
<CabinLayout> | |||||||
CabinLayout | Row Details of the Cabin | M | |||||
XML Example for the following elements
| |||||||
Columns | Seat column to identify a particular seat position on an aircraft | M | |||||
Rows | Contains rows and seat information for seat display purposes | M | |||||
First | First-row number | M | |||||
Last | Last row number | M | |||||
ExitRowPosition | Return the exit row information, if applicable. This must be returned regardless of whether exit row seats are open or are returned as valid seats | O | |||||
RowPosition | EXIT row detail | M | |||||
First | Exit seat starting row position | M | |||||
Last | Exit seat ending row position | M | |||||
<Component> | |||||||
Component | Non-Seat Cabin Component information like Jump Seat, Galley, Lavatory, Door etc.. This is where the non-seat characteristics are returned | O | |||||
XML Example for the following elements
| |||||||
Type | Cabin component | M | |||||
Location | The physical location of the cabin component | M | |||||
RowPosition | A range of rows covered by a non-seat cabin component for seat map information. | M | |||||
Begin | Non-seat's row position | M | |||||
End | M | ||||||
ColumnPosition | Column position of the Non-Seat Component | M | |||||
<Row> | |||||||
Row | Seat row | M | |||||
XML Example for the following elements
| |||||||
Number | Seat Row Number | M | |||||
Seat | SEAT Info. This consist of a information of list of Seat which comes in a same row. | M | |||||
Column | Column number of the Seat | M | |||||
SeatStatus | Seat status | M | |||||
SeatCharacteristics | Seat information | ||||||
Code | Refers to aircraft seat characteristics; seat option codes | M | |||||
OfferItemRefs | Reference to the AlaCataOfferItem applicable to this individual seat. Multiple seats can reference the same AlaCataOfferItem. | M | |||||
<DataLists> | |||||||
<PassengerList> | |||||||
PassengerList | Passenger data list definition/details. | M | |||||
XML Example for the following elements
| |||||||
Passenger | Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship | M | |||||
PassengerID (Attribute) | Uniquely identifies a Passenger within the context of one message. | M | |||||
PTC | Type code applying to the Passenger which typically drives pricing Example: ADT, CHD, etc | M | |||||
<ServiceDefinitionList> | |||||||
ServiceDefinitionList | Service definition list which has been offered. | M | |||||
XML Example for the following elements
| |||||||
ServiceDefinition | Service Definition Detail | O | |||||
ServiceDefinitionID (Attribute) | A unique Service ID that has been returned in the Shopping results, and identifies an airline service item (ie a product or a service) that can be separately delivered and uniquely described by an airline. Example : V1_SEATSSR_1549440901033 | O | |||||
Name | Example : SEAT SELECTION | O | |||||
Encoding | Service Codes and Reason for Issuance. | O | |||||
RFIC | Reason For Issuance Code | O | |||||
Code | Service code. | O | |||||
SubCode | Associated Reason For Issuance Sub Code | O | |||||
FeeMethod | Two character generic code to identify ticket | O | |||||
Descriptions | SERVICE Description. | O | |||||
Description | Service Description detail. | O | |||||
Text | Description value. | O | |||||
Application | Description Application | O | |||||
Settlement | Interline Settlement information between airlines, including method of settlement,interline settlement value and currency. | O | |||||
Method | Service settlement method. | O | |||||
<FlightSegmentList> | |||||||
FlightSegmentList | Flight segment details for the requested itinerary | O | |||||
| |||||||
FlightSegment | Flight Segment | M | |||||
SegmentKey (Attribute) | A globally unique identifier for this Flight Segment instance. | M | |||||
ElectronicTicketInd (Attribute) | When true, an electronic ticket may be issued. | O | |||||
Departure | Departure (origin) Airport, Date and Time information. (en, description) | M | |||||
AirportCode | Airport or a city code. Use a three letter location identifier assigned according to the IATA Resolution 763. Refer to IATA Airline Coding Directory . Example: TPA | M | |||||
Date | Departure date. Example: 2017-01-13 Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) | M | |||||
Time | Departure time. Example: 09:15 Encoding Scheme: ISO 8601 Military/ 24 Hour Format (HH:MM) | O | |||||
Terminal Information | Terminal information will be present under the Departure and Arrival tags only if the terminal information is available in the flight | O | |||||
Arrival | Arrival (destination) Airport, Date and Time information. | M | |||||
AirportCode | Airport or a city code. Use a three letter location identifier assigned according to the IATA Resolution 763. Refer to IATA Airline Coding Directory . Example: TPA | M | |||||
Date | Arrival date. Example: 2017-01-13 Encoding Scheme: ISO 8601 Date Format (YYYY-MM-DD) | O | |||||
Time | Arrival time. Example: 09:15 Encoding Scheme: ISO 8601 Military/ 24 Hour Format (HH:MM) | O | |||||
MarketingCarrier | Marketing Carrier information | M | |||||
AirlineID | A two-character alpha-numeric code assigned according to the IATA Resolution 762 or a three-letter airline designator assigned by ICAO. Refer to IATA Airline Coding Directory . | M | |||||
FlightNumber | Flight Number. Example: 1234, or OPEN, or ARNK | M | |||||
Equipment | Aircraft Equipment. | M | |||||
AircraftCode | The IATA aircraft type 3 character code; use SSIM Appendix A. Example:318. | M | |||||
AirlineEquipCode | Airline-specific aircraft equipment code. Example: 737-800 | O | |||||
ClassOfService | Class of Service. Example: T | M | |||||
Code | Class of Service Code | M | |||||
FareBasisCode | Fare basis code. Example: Y26CH | O | |||||
FlightDetail | Flight Details. | O | |||||
FlightDuration | Flight Duration with application. | M | |||||
Stops | Flight Stop Quantity and Location(s). | O | |||||
StopQuantity | Stop Quantity. Example: 1 | O | |||||
<FlightList> | |||||||
FlightList | FlightList details for the requested itinerary | M | |||||
| |||||||
Flight | Journey information describing the travel between an airport/city where travel commences and an airport/city where travel ultimately terminates. A journey may be comprised of one or more segments. Note: This node will be renamed to journey in future releases. | M | |||||
FlightKey (Attribute) | A globally unique identifier for this Flight instance. | O | |||||
Journey | Flight journey information. | O | |||||
Time | Total Journey Time. Example: PT7H45M (7 hours and 45 minutes) Note: Total journey time includes the combined air time, connection time and/ or stop information for all specified flight segments | O | |||||
SegmentReferences | Association to multiple Flight Segment instance(s). Example: segment1 segment2 Note: Flight Slice On and Off Board Points may also be specified. | M | |||||
<OriginDestinationList> | |||||||
OriginDestinationList | OriginDestinationList details for the requested itinerary | M | |||||
| |||||||
OriginDestination | Origin/ Destination information. Contains a list of all Flight element that are part of that OD. | M | |||||
OriginDestinationKey | A globally unique identifier for this OriginDestination instance. | O | |||||
DepartureCode | Departure (origin) Airport Code. | M | |||||
ArrivalCode | Airport or a city code. Use a three letter location identifier assigned according to the IATA Resolution 763. Refer to IATA Airline Coding Directory . Example: TPA | M | |||||
FlightReferences | Association to multiple Flight instance(s). Example: V1_FL.1605138125285 | M | |||||
OnPoint (Attribute) | Flight slice on point. | O | |||||
OffPoint (Attribute) | Flight slice off point. | O |