AirLabs Data API
★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey17 EndpointsREST
For Agents
Look up live flights, airport and airline reference data, schedules, delays, and routes from the AirLabs aviation database.
Use for: Get the current status of flight BA245, I want to find airports near a specific city, List delayed flights at a specific airport, Search for an airport by name
Not supported: Does not handle flight booking, ticketing, or seat selection — use for live tracking, schedules, and aviation reference data only.
Jentic publishes the only available OpenAPI specification for AirLabs Data API, keeping it validated and agent-ready. AirLabs provides real-time and reference aviation data covering live flight tracking, airport and airline databases, schedules, delays, routes, fleets, and timezone reference data. The API exposes 17 endpoints suitable for travel apps, dashboards, and operational tools. Authentication uses an API key passed as the api_key query parameter.
Install Jentic One Beta
Connect the AirLabs Data API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AirLabs Data 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 AirLabs Data API.
Pull real-time flight positions and tracking data via /flights
Fetch flight-level details (status, schedule, aircraft) via /flight
Look up airport, airline, city, country, and aircraft fleet reference data
Query global flight schedules and delay reports filtered by airport or airline
Find airports near a geographic point using /nearby
Search the airport autocomplete index via /suggest for typeahead UIs
Create flight alerts to be notified of status changes
Use Cases
Patterns agents use AirLabs Data API for, with concrete tasks.
★ Live Flight Tracking Dashboard
Power a flight tracking dashboard with live aircraft positions and per-flight detail. GET /flights returns the active aircraft set with bounding-box and airline filters, and GET /flight returns full status, route, and aircraft information for a specific flight identifier.
Fetch all flights operating between LHR and JFK right now, then for each flight return its current altitude, speed, and estimated arrival time
Airport and Schedule Reference
Build a travel-planning experience that lets users search airports, view schedules, and check delays. /suggest powers airport autocomplete, /schedules returns scheduled departures and arrivals filtered by airport, and /delays surfaces problem flights for an airport on a given day.
Search airports matching 'San Francisco', then list scheduled departures from SFO for the next 6 hours along with any current delays
Flight Status Alerts
Notify users when a tracked flight's status changes. POST /alert registers an alert against a flight identifier and contact channel, and the alerting service pushes an update when the flight is delayed, cancelled, or arrives.
Create a flight alert for flight UA1234 on 2026-06-15 with email recipient ops@example.com so any delay or gate change triggers a notification
AI Agent Travel Concierge
An agent embedded in a travel concierge product can pull live flight status, suggest airports, and trigger alerts on the user's behalf — all through Jentic. The api_key query parameter stays in the vault and only scoped operations are exposed.
Search Jentic for 'get flight status', load the GET /flight schema, and return current status for flight LH404 including any delay reason
Key Endpoints
17 endpoints — jentic publishes the only available openapi specification for airlabs data api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/flights
Real-time flight positions
GET
/flight
Detailed information for a specific flight
GET
/schedules
Scheduled flights for an airport or airline
GET
/delays
Currently delayed flights
GET
/airports
Airport reference database
GET
/airlines
Airline reference database
GET
/nearby
Find airports near a geographic point
POST
/alert
Create a flight status alert
GET
/flights
Real-time flight positions
GET
/flight
Detailed information for a specific flight
GET
/schedules
Scheduled flights for an airport or airline
GET
/delays
Currently delayed flights
GET
/airports
Airport reference database
GET
/airlines
Airline reference database
GET
/nearby
Find airports near a geographic point
POST
/alert
Create a flight status alert
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The AirLabs api_key is stored encrypted in the Jentic vault. Jentic appends it as a query parameter on every call, so it does not appear in agent prompts or model context.
Intent-based discovery
Agents search Jentic by intent (e.g. 'get flight status') and Jentic returns the matching AirLabs operation with its input schema, no documentation browsing required.
Time to first call
Direct AirLabs integration: 4-8 hours for auth, query parameter handling, and pagination of large reference endpoints. Through Jentic: under 15 minutes.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AirLabs Data API through Jentic.
Why is there no official OpenAPI spec for AirLabs Data API?
AirLabs does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AirLabs Data API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the AirLabs Data API use?
AirLabs uses an API key passed as the api_key query parameter on every request. Jentic stores the key encrypted in the vault and appends it at call time, so the raw key is never visible to the agent.
Can I get the live position of all flights with the AirLabs API?
Yes. GET /flights returns active flights with position, altitude, and speed; the response can be filtered by bounding box, airline, or aircraft type to keep payload sizes manageable.
What are the rate limits for the AirLabs Data API?
Rate limits are tied to the AirLabs subscription plan rather than declared in the spec. For high-frequency tracking, throttle /flights polling to once every 30-60 seconds and use /flight for on-demand detail rather than per-second polling.
How do I look up airport information with the AirLabs API through Jentic?
Run pip install jentic, search Jentic for 'airlabs airport lookup', load the schema for GET /airports, then execute with the IATA or ICAO code. Jentic appends the api_key automatically.
Can I create alerts for flight delays via the AirLabs API?
Yes. POST /alert registers an alert tied to a flight identifier and contact channel; AirLabs notifies the recipient when the flight's status changes.
GET STARTED