Look up airline details by IATA code via pay-per-request Amadeus reference data
What it does
This endpoint is part of StableTravel's reference data suite, which wraps the Amadeus GDS API behind a pay-per-request micropayment wall. The `/api/reference/airlines` endpoint accepts a GET request with an optional `airlineCodes` query parameter (comma-separated IATA airline codes) and returns airline information from Amadeus. It costs $0.0054 per request, paid via MPP (Tempo on chain 4217) or x402 protocol using USDC. No API keys, OAuth tokens, or subscriptions are required — payment serves as authentication.
StableTravel exposes a broad travel API surface beyond this single endpoint: flight search and booking (Amadeus GDS), Google Flights price comparison, hotel search and booking, activities/tours, airport transfers, real-time flight tracking (FlightAware AeroAPI), airport weather (METAR/TAF), flight history, and disruption statistics. All endpoints follow the same pay-per-request model with prices ranging from $0.001 to $0.40 per call. The full OpenAPI 3.1 spec is available at `/openapi.json`.
The airline lookup endpoint is useful as a utility call to resolve IATA codes (e.g., "AA", "DL", "UA") into full airline names and metadata. It pairs naturally with flight search, route lookup, and flight status endpoints in the same API suite. Payment is handled automatically by compatible MPP/x402 clients such as `npx agentcash fetch`.
Capabilities
Use cases
- —Resolve IATA airline codes to full airline names and details when processing flight search results
- —Enrich flight itinerary displays with airline metadata
- —Validate airline codes before submitting flight search or booking requests
- —Build airline autocomplete or selection UIs backed by authoritative GDS data
- —Cross-reference carrier codes in disruption or delay reporting workflows
Fit
Best for
- —AI travel agents that need to resolve airline codes on the fly
- —Autonomous booking pipelines that validate carrier information before booking
- —Reference data enrichment in multi-step flight search workflows
Not for
- —Bulk airline database dumps — this is a per-request lookup, not a batch export
- —Flight booking or ticketing — use the /api/flights/book endpoint for that
- —Real-time flight tracking — use the FlightAware endpoints instead
Quick start
npx agentcash fetch "https://stabletravel.dev/api/reference/airlines?airlineCodes=AA,DL"Example
Response
{
"data": [
{
"type": "airline",
"iataCode": "AA",
"icaoCode": "AAL",
"commonName": "American Airlines",
"businessName": "AMERICAN AIRLINES"
}
],
"meta": {
"count": 1
}
}Endpoint
Quality
Full OpenAPI 3.1 schema with x-payment-info, live 402 MPP challenge captured, comprehensive guidance docs, and clear pricing. Response schema for this specific endpoint uses generic `items: {}` rather than detailed field definitions, and no example response is provided in the spec, so the example_response_json is inferred from Amadeus conventions.
Warnings
- —Response schema for /api/reference/airlines uses untyped `items: {}` — actual response fields are inferred from Amadeus API conventions
- —The example_response_json is illustrative and not sourced from a live call or documented example
Citations
- —Endpoint price is $0.0054 per request (amount 5400 in base units on Tempo chain 4217)https://stabletravel.dev/openapi.json
- —Payment via MPP method tempo with intent charge, or x402 protocolhttps://stabletravel.dev/openapi.json
- —airlineCodes parameter accepts comma-separated IATA airline codeshttps://stabletravel.dev/openapi.json
- —No API keys needed — payment via USDC on Base, Solana, or Tempo serves as authenticationhttps://stabletravel.dev
- —Part of StableTravel suite with flights, hotels, activities, transfers, and FlightAware datahttps://stabletravel.dev