Contents x
Download the latest standards
  • 19 Dec 2022
  • 5 Minutes to read
  • Contributors
  • Print
  • Dark
    Light
  • PDF
Contents

Download the latest standards

  • Updated on 19 Dec 2022
  • 5 Minutes to read
  • Contributors
  • Print
  • Dark
    Light
  • PDF

22.4 Data Exchange Standards Release

This page provides access to the last agreed content of the data exchanges standards. 

All data exchange standards being developed today under the governance of the PSC (Resolution 009) and are required to use the Airline Industry Data Model (AIDM) and associated methodology. 

22.4 XML and API Standards Messages

Following section highlight the main changes for the release publication package, this is an augmented version from the previous release publication, if you need more information on that content, do not hesitate to send a request to our mailbox AIDM@IATA.ORG

22.4includes 2 changes Request + new Code set category (FQQ = Fuel Quantity Qualifier) + 3 defects from baseline 21.3 for Offers and Orders messages.
- CR (190) from Load Control Group for the Semi-Permanent Data Message with new elements from DOW configuration  
- CR (191) from Operational Fuel Notification Group for the Fuel Notification Message with new elements for Fuel Quality
View schemas updated for this release in this spreadsheet : 22.4 Release note changes by release

22.4 XML and API Standards Messages


22.4 Code Set Directory

This document provides the agreed Codeset utilized by the Airline industry for the identification of information included within IATA standard messages.
The codeset directory is designed to be used by both the EDIFACT as well as the XML messages.

22.4 List of Data Exchange Standards by Board

This document provides the list of Standards Data Exchanges Messages by PS Boards.

22.4 Passengers Glossary of Terms

This document provides glossary of terms for Passengers as defined in PSCM RP1008

22.4 JSON library of AIDM Objects 

This document provides the standards Open Air JSON library 22.4 in the beta version including objects sourced from the AIDM Governance Models. The library can be consumed by any relevant industry parties for evaluation purposes.

The requirements and Consumption Guide have been developed by Open API Group. 

View archived Data Exchange Standards for previous Releases

ReleaseAIDM ExportXML & API Standards
22.3XMI Export

22.3 XML and API Standards Messages

Note to the implementers:
22.3 Release has no Changes on Data Exchange Standards Messages from previous Release Cycle 22.2 (except few updates on codeset Library) 
22.2XMI Export

22.2 XML and API Standards Messages

Note to the implementers:
22.2 includes a single change on the IATA_InterlineOfferRQ Schema to add “DistributionChannel" structure into the root node .  
View schemas affected for this release in this spreadsheet : 22.2 Release note changes by release
Please use this build for the latest schemas released.
22.1XMI Export

22.1 XML and API Standards Messages

Note to the offers and orders implementers:
22.1.1 includes the latest fixes related to Offer & Order messages critical issues for 21.3 baseline.  
22.1.2 includes a minor correction within the Baggage and Passenger Conformance messages to add a missing end tag in the comment section, and a minor correction on the message IATA_TicketGroundHandlingChangeOfStatusRQ.TicketDocument.CouponInfo to remove a duplicated reference to CompanyID in the same node 
Note to the settlement with orders implementers:
22.1.3 includes a typo in the annotation of the namespace for schema “IATA_PaymentClearanceCancellationRS”, which refers to the “IATA_PaymentClearanceCancellationRQ” in the namespace. Please note that this misprint has no consequence on the structure of the “IATA_PaymentClearanceCancellationRS” schemas, which correctly refers to the Common Types used for all SwO schemas in the data structure “IATA_PaymentClearanceCommonTypes”
21.4XMI Export

21.4 XML and API Standards Messages

21.4 includes some changes on Schedules SDEX schemas to add new "Passenger Health Information"  PaxHealthText and amend existing annotation for the SecureFlightInd.
21.4.1 includes some patches applied within the Offer & Order messages. Please use this build for your upcoming convergence release.
Note to Settlement with Orders Implementers:
21.4.2 includes a typo in the annotation of the namespace for schema “IATA_PaymentClearanceCancellationRS”, which refers to the “IATA_PaymentClearanceCancellationRQ” in the namespace. Please note that this misprint has no consequence on the structure of the “IATA_PaymentClearanceCancellationRS” schema, which correctly refers to the Common Types used for all SwO schemas in the data structure “IATA_PaymentClearanceCommonTypes”
21.3XMI Export

21.3 XML and API Standards Messages

Note to Offer and Order Implementers:
21.3. includes first version of interline schemas for Offers and Orders Requests, new API (JSON) for Common use web service for Passenger Boarding pass validation, deletion of 3 schemas OrderCancelRQ/RS and InvReleaseNotifRQ and also included many changes related to Offers and Order schemas to create new 21.3 Baseline for Offers and Orders.
21.3.1 includes a minor patch to remove key/keyrefs which were incorrectly causing some validation issues. The data model has not been changed. The intention is still to maintain the integrity of IDs which will be defined in the implementation guide.
21.3.2 includes some (critical) patches applied within the Offer & Order messages. Please use this build for your upcoming convergence release.
Note to Settlement with Orders Implementers:
21.3.3 includes a typo in the annotation of the namespace for schema “IATA_PaymentClearanceCancellationRS”, which refers to the “IATA_PaymentClearanceCancellationRQ” in the namespace. Please note that this misprint has no consequence on the structure of the “IATA_PaymentClearanceCancellationRS” schema, which correctly refers to the Common Types used for all SwO schemas in the data structure “IATA_PaymentClearanceCommonTypes”
 21.3.4 includes 3 new defects into the baseline 21.3 of Offers and Orders Messages as defined below: 
  • Defect EASD-321 for Fix Correction of OSIADN to a Baseline configuration 
  • Defect EASD-333 for Fix Correction of "Owner code" from mandatory to optional at OrderItem Level in OrderRequest element
  • Defect EASD-319 for Fix Correction of Six Digit "IIN” back to shopping and pricing messages 
Please use this build for the latest schemas released 
21.2XMI Export21.2 XML and API Standards Messages
includes some changes on the IATA_AIDX FuelCommonTypes & IATA_AIDX_FlightLegNotifRQ schema messages to correct a minor defect introduced with 21.1 where density units were incorrectly implemented, and addition of digital signature (eDisg) 
21.1XMI Export21.1 XML and API Standards Messages
21.1 includes new Offer and Order XML schema "IATA_OrderQuoteRQ" for order reshop / order price, new technical architecture to share common types elements accross Offers and Order schemas with file named as "IATA_OffersAndOrdersCommonTypes", amend "IATA_BagEventNotifRQ" with new "Containerization Status Code",minors enhancements to the AIDX schemas (IATA_AIDX_CommonTypes & IATA_AIDX_FuelCommonTypes) to clarify Fuel activity and new code set updates.
20.2XMI Export20.2 XML and API Standards Messages
20.2 includes new Settlements with Order Schemas (IATA_PaymentClearingNotifRQ, IATA_PaymentClearingListRQ/RS), new AIDX towing messages (IATA_FlightLegLinkGroundMovementRQ/RS), new API(JSON) for NDC IATA_EasyPay Direct Authorization and few changes for Offer and Orders Messages  
20.1XMI Export20.1 XML and API Standards Messages
20.1 includes first schemas for Settlement with Orders (PaymentClearanceListRQ/RS, PaymentRemittanceListRQ/RS, PaymentSettlementListRQ/RS, PaymentClearanceCancellationRQ/RS), new API's (JSON) for API 1 for Agent Validation and API 2 for Real Time Sales Monitoring and API 3 for Transparency in Payment, and few changes for Offers and Orders Messages and Baggage schema , minor correction of Load Control AHM565 Message and minor update on legacy message for SXSG and AIDX Fuel Data Standard message. 
19.2XMI Export19.2 XML and API Standards Messages
19.2 includes new schema for Ground Operation for Aircraft Registration (IATA_OperationalAircraftRegistrationNotif) and ome enhancements on Offers and Orders schemas, minor updates on the Baggage and Load Control schemas (AHM565) and minor changes on legacy Slot/Schedules Schemas (SXSG)
19.1XMI Export19.1 XML and API Standards Messages
19.1 includes new schemas for Product Flight Availability (IATA_DailyFlightAvailabilityRQ/RS, IATA_SeamlessAvailabilityRQ/RS), some enhancements on Offers and Orders schemas, minor updates on the Baggage and Load Control schemas (AHM565) and decommissioning of AirDocIssueRQ Message.
18.2XMI Export18.2 XML and API Standards Messages
18.2 includes new schemas for One Order first baseline for Offer and Orders (IATA_UpdateServiceNotifRQ, IATA_ServiceStatusChangeNotifRQ, IATA_ServiceDeliveryRS, IATA_ServiceDeliveryRQ, IATA_ServiceDeliveryNotifRQ, IATA_OrderSalesInformationNotifRQ, IATA_OrderClosingNotifRQ) and enhancements on existing schemas (IATA_OrderListRQ, IATA_OrderRetrieveRQ, IATA_OrderViewRS, 

Order RulesRQ/RS, AirlineProfileNotif/RQ/RS, AirDocIssueRQ, Acknowledgement, OrderChangeNotif), some changes on legacy XML messages on Ticketing, Baggages and PNRGOV and minor correction of the Load Control (AHM565) Schema.

18.1XMI Export
Was this article helpful?
What's Next

DISCLAIMER: The information contained in this publication is subject to constant review in the light of changing government requirements and regulations. No reader should act on the basis of any such information without referring to applicable laws and regulations and/or without taking appropriate professional advice. Although every effort has been made to ensure accuracy, the International Air Transport Association shall not be held responsible for any loss or damage caused by errors, omissions, misprints or misinterpretation of the contents hereof. Furthermore, the International Air Transport Association expressly disclaims any liability to any person or entity in respect of anything done or omitted, by any such person or entity in reliance on the contents of this publication.