Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Data Enrichment / Amadeus / Airline Code Lookup API
Airline Code Lookup API logo

Amadeus Airline Code Lookup API

Browse all Amadeus APIs
0
AI ReadinessNon-Ready (F)0/100
See full scorecard
Official vendor OpenAPI document · agent-readyData 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.

Jentic One on GithubView OpenAPI Document

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Famadeus.com%2Famadeus-airline-code-lookup" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famadeus.com%2Famadeus-airline-code-lookup" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

A

Airline Code Lookup API

- Non-Ready (F)
0/100
100
Foundational Compliance
78
Developer Experience & Jentic Compatibility
41
AI-Readiness & Agent Experience
94
Agent Usability
100
Security
0
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

78

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4
39%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

41

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4
48%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

17%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1
100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

0

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: FSignals: 1
0%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Airline Code Lookup API by hand means running Amadeus OAuth2 to get a token, targeting the test.api.amadeus.com/v1 host, and refreshing that token yourself. Through Jentic you install once, import the Airline Code Lookup API from the API Directory, store the OAuth2 credentials once, and your agent calls it.

Permission scoping

The Airline Code Lookup API exposes a single read-only /reference-data/airlines endpoint whose codes travel as query parameters rather than a path resource, so limit the agent to that one operation. You choose whether the agent may call it, and no other operations exist to add.

Credential isolation

Your Amadeus OAuth2 credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'resolve an IATA airline code to a carrier name', and Jentic returns the matching Amadeus operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Amadeus Airport Nearest Relevant

→

Returns the nearest commercial airports to a given coordinate, often used together with airline lookups when building flight UIs.

Pair with airline lookup when the agent also needs to resolve nearby airports for a search context.

Complementary

Amadeus Flight Check-in Links

→

Returns the official check-in URL for a given carrier - uses the same airline code that the lookup resolves.

Use after airline lookup when the agent needs to send a check-in link for that carrier.

Complementary

Amadeus Flight Availabilities Search

→

Provides flight availability whose results carry IATA codes that the lookup resolves to names.

Use the lookup as a post-processing step on the availability response to display readable carrier names.

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.

Can I limit what my agent is allowed to do with the Airline Code Lookup API?

Yes. This API exposes a single read-only operation, GET /reference-data/airlines, which resolves IATA or ICAO codes passed as query parameters, so there is exactly one call to grant. Because Jentic One is self-hosted, you run it under your own rules and decide whether your agent may invoke that lookup at all, and the encrypted Amadeus OAuth2 credentials are injected at execution time rather than handed to the agent. Since no other operations exist on this API, scoping it comes down to allowing or withholding that one read-only lookup.

GET STARTED

Start building with Airline Code Lookup API

Explore with Jentic One
View OpenAPI Document