IATA Developer Profile

Timatic AutoCheck is a solution that verifies traveller documentation and checks if it is sufficient for the whole journey. When documents related to passengers' destination/transit are not sufficient, Timatic provides details about the travel rules and required documents. This is technical documentation for anyone involved in interfacing with Timatic via REST API.

IATA

REST

Federated

European FEDeRATED project

The official industry standard for pricing and ticketing transactions when converting fares, taxes, and fees to an alternate currency. Note: By clicking the "Test Endpoint" below, you connect to the sandbox API.

A Collection of APIs allowing validation of IATA Numeric Codes and associated Sellers' details.

A Collection of APIs allowing validation of IATA Travel Agent credentials (ID Cards) and associated details.

This site outlines the API of the IATA Turbulence Aware Platform.

The information herein provides the technical specifications of the IATA CO2 Connect File™ REST API. The API returns a CSV file with CO2 emissions values for various aircraft types.

REST

IATA

mock

BSP Risk Monitoring Agency Sales Transactions

Also known as API2. In order for IATA to perform risk monitoring activities on an Agency in the context of BSP, the NDC Airline needs to send to IATA a set of sales data corresponding to the transaction just issued feeding the IATA internal risk monitoring engine.

IATA CO2 Connect is an emissions calculator developed with real airline data based on industry approved recommended practices . The information herein provides the technical specifications of the IATA CO2 Connect™ REST API. The API calculates CO2 emissions values for various airlines, aircraft types & cabin classes.

This OpenAPI specification describes the API endpoint structure of an ONE Record API implementation. To try the ONE Record API, please use the Playground API https://api.developer.iata.org/iata-iata-cargo/api/one-record-playground. More information about the ONE Record specification are available on IATA Github repository (https://github.com/IATA-Cargo/ONE-Record) and on the ONE Record API specification website (https://iata-cargo.github.io/ONE-Record/).

REST

IATA

spec only

BSP Risk Monitoring Agency Profile

Also known as NDC API1. At the time of offer and order management, the NDC Airline needs to know the up-to-date status of the Agency requesting transaction issuance. The Airline sends a request to IATA about an agency risk profile using the Agency code. In return, IATA provides the Airline with the status of Agency and Agency risk information, including Airline ticketing authority granted or not by the Airline to that Agency.

ONE Record Playground

The IATA ONE Record playground is safe space where airline industry developers can gain experience on ONE Record standard

sandbox

REST

NDC EasyPay Direct Authorisation

Prior to accepting IATA EasyPay or BOP form of payment details provided by a seller through the NDC messages, airlines need to obtain an authorisation in order to make sure the required funds of the seller will be blocked for later settlement. This API can be used by airlines to obtain such authorisation and, if the transaction will never be settled, revert the authorisation to unblock the seller’s funds.

Automate your NOTOC creation using DG AutoCheck Connect API.

IATA

Discussions