Amadeus Airline Code Lookup API
Browse all Amadeus APIs✓ Official Vendor SpecData EnrichmentData Transformationoauth21 EndpointsREST
For Agents
Resolve IATA or ICAO airline codes to full carrier names. Agents call /reference-data/airlines to translate codes like BA into 'British Airways' for human-readable output.
Use for: I want to translate the airline code BA to a full carrier name, Look up the airline name for IATA code AF, Find all carrier names for a list of IATA codes returned by a flight search, Get the ICAO code for British Airways
Not supported: Does not return flight schedules, fares, or availability — use for resolving IATA and ICAO airline codes to carrier names only.
The Amadeus Airline Code Lookup API resolves IATA and ICAO airline codes to full carrier names and metadata. Given a code such as BA or AAL, it returns the carrier's commercial name and identifier mappings, which is essential for displaying human-readable airline names in flight search results, itineraries, and reporting. The single GET endpoint at /reference-data/airlines is read-only and is typically used as an enrichment step alongside Amadeus flight shopping APIs.
Install Jentic One Beta
Connect the Airline Code Lookup API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Airline Code Lookup API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Airline Code Lookup API.
Resolve an IATA code such as BA to the carrier's commercial name
Resolve an ICAO three-letter code such as AAL to the carrier's commercial name
Look up multiple airline codes in a single GET request via the airlineCodes query parameter
Map between IATA and ICAO identifiers when displaying flight search results
Enrich itinerary records with carrier names before sending them to a customer
Use Cases
Patterns agents use Airline Code Lookup API for, with concrete tasks.
★ Itinerary Display Enrichment
Translate IATA airline codes returned by Amadeus Flight Offers Search into the carrier's full commercial name before showing the itinerary to a traveller. The /reference-data/airlines GET endpoint accepts comma-separated codes and returns business names in a single round trip, which is faster than maintaining a static carrier table that drifts out of date.
Call /reference-data/airlines with airlineCodes=BA,AF,LH and return a map of code to carrier name.
Reporting and Reconciliation
Reports that aggregate flight bookings or fares by carrier need consistent carrier names, not ambiguous two-letter codes. The lookup API gives finance and revenue teams a single source of truth for carrier identifiers, so monthly travel reports can group spend by airline reliably even when the flight system records only the IATA code.
Resolve every distinct airline code in last month's bookings dataset to a carrier name and group spend by carrier.
Validating User-Supplied Codes
When a traveller types an airline code into a search box, validate it against the Airline Code Lookup before passing it to a downstream flight offer search. This catches typos early and gives the traveller a clearer error message than a 400 response from the flight search endpoint.
Verify that the user-supplied code XJ resolves to a known carrier and surface the carrier name back to the user.
Agent Itinerary Generation
Let an AI travel agent enrich raw flight offers with carrier names automatically. Through Jentic the agent searches for 'translate airline code to name', loads the schema, and calls the lookup with the codes pulled from a Flight Offers response. The carrier names are then woven into the natural-language itinerary the agent returns to the user.
Use Jentic to find the airline lookup operation, pass the list of codes from the flight search, and produce a natural-language itinerary with carrier names.
Key Endpoints
1 endpoints — the amadeus airline code lookup api resolves iata and icao airline codes to full carrier names and metadata.
METHOD
PATH
DESCRIPTION
GET
/reference-data/airlines
Resolve IATA or ICAO airline codes to carrier names
GET
/reference-data/airlines
Resolve IATA or ICAO airline codes to carrier names
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Amadeus client ID and secret are stored encrypted in the Jentic vault (MAXsystem). Jentic exchanges them for a short-lived bearer token at execution time so the raw secret never reaches the agent.
Intent-based discovery
Agents search Jentic with phrases like 'translate airline code to name' and Jentic returns the /reference-data/airlines operation with its input schema, removing any need to read Amadeus self-service docs first.
Time to first call
Direct Amadeus integration: half a day to wire OAuth, the request, and error handling. Through Jentic: under fifteen minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Airline Code Lookup API through Jentic.
What authentication does the Airline Code Lookup API use?
The API uses the Amadeus OAuth 2.0 client-credentials flow. Exchange your API key and secret at the Amadeus token endpoint, then send the resulting bearer token as Authorization: Bearer on the /reference-data/airlines call. Through Jentic the client credentials live in the encrypted vault and the bearer token is never exposed to the agent.
Can I look up multiple airline codes in one request?
Yes. The /reference-data/airlines endpoint accepts a comma-separated airlineCodes query parameter, so you can resolve a batch of codes returned by a flight offers search in a single round trip rather than one call per carrier.
What are the rate limits for the Airline Code Lookup API?
The OpenAPI specification does not declare rate limits. Amadeus applies a transactions-per-second cap that varies by API and contract tier — verify the exact limit for your account in the Amadeus self-service portal before relying on burst traffic.
How do I resolve an airline code through Jentic?
Run pip install jentic, then search Jentic for 'translate airline code to name'. The Airline Code Lookup operation surfaces with its input schema; pass airlineCodes=BA,AF and execute. Jentic handles the OAuth token refresh against the Amadeus auth server.
Does the Airline Code Lookup return ICAO as well as IATA codes?
Yes. Each result includes both the IATA two-letter code and the ICAO three-letter code, so a single lookup can be used to convert between the two identifiers when needed for downstream systems that expect ICAO.
Is the Airline Code Lookup API free?
Amadeus self-service APIs include a free test environment with quota limits and a paid production tier. Production access requires a contract with Amadeus and pricing scales with transaction volume — confirm current rates in the Amadeus self-service developer portal.
GET STARTED