Flightradar24 API

Name: Flightradar24 API
Brand: Flightradar24 API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentCompany Databearer16 EndpointsREST

For Agents

Look up live and historical flight positions, flight summaries, flight tracks, and airline and airport metadata across Flightradar24's tracking corpus.

Install Jentic One Beta

Connect the Flightradar24 API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flightradar24 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.

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 | sh

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 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 Flightradar24 API.

Pull live flight positions worldwide with light or full payload variants

Query historical flight positions back to May 11, 2016 with the same light or full variants

Retrieve flight summaries by flight, callsign, route, or registration

GET STARTED

Start building with Flightradar24 API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Flightradar24 API for, with concrete tasks.

★ Live flight tracking dashboard

Travel apps and operations teams build live flight tracking dashboards by polling /api/live/flight-positions/light or /api/live/flight-positions/full. The light variant keeps bandwidth low for map overlays, while the full variant adds aircraft type, airline, registration, and route detail for richer detail panes. Combined with /api/static/airlines and /api/static/airports lookups, this drives a complete arrivals or departures board.

Fetch live full flight positions inside a bounding box covering the UK and return aircraft callsign, type, altitude, and ground speed for each result

Historical flight analysis

Analysts reconstruct past flights by querying /api/historic/flight-positions and /api/flight-tracks for any date back to May 11, 2016. The historical event endpoints add takeoff, landing, and diversion markers so that delay-cause analysis, accident investigations, and academic research can rebuild a flight's timeline minute by minute.

Pull the full flight track for a specific aircraft registration on 2024-08-12 and return latitude, longitude, altitude, and timestamp for each point

Airline operations reporting

Airlines and ground handlers pull /api/flight-summary/full and /api/historic/flight-events to assemble daily on-time performance reports, delay attributions, and route utilization summaries. The light and count variants of the same endpoints support efficient totals queries before drilling into the full record.

Get the count and full flight summaries for airline ICAO BAW on 2024-12-01 and group results by departure airport

AI agent travel disruption assistant

An AI travel agent uses Flightradar24 through Jentic to look up the current position of a passenger's flight, check whether it has diverted using the historic flight events feed, and explain expected delay times. Jentic returns the right Flightradar24 operation per intent, so the same agent skill handles live and historical questions without extra code paths.

Given flight number AA100 today, return its live position, ground speed, and any diversion event in the last 6 hours

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for flightradar24 api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/live/flight-positions/full

Live aircraft positions with full record

GET

/api/live/flight-positions/light

Live aircraft positions with reduced payload

GET

/api/historic/flight-positions/full

Historical aircraft positions back to 2016

GET

/api/flight-summary/full

Per-flight summary records with full detail

GET

/api/flight-tracks

Recorded flight track for a specific flight

GET

/api/historic/flight-events/full

Historical flight event markers

GET

/api/static/airlines/{icao}/light

Airline metadata lookup by ICAO code

GET

/api/usage

Read account API usage and quota stats

GET

/api/live/flight-positions/full

Live aircraft positions with full record

GET

/api/live/flight-positions/light

Live aircraft positions with reduced payload

GET

/api/historic/flight-positions/full

Historical aircraft positions back to 2016

GET

/api/flight-summary/full

Per-flight summary records with full detail

GET

/api/flight-tracks

Recorded flight track for a specific flight

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Flightradar24 token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'track a live flight' or 'get a flight summary', and Jentic returns the matching Flightradar24 operation with its input schema so the agent calls the right variant without browsing the reference docs.

Time to first call

FAQs

Specific to using Flightradar24 API through Jentic.

Why is there no official OpenAPI spec for Flightradar24 API?

Flightradar24 does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Flightradar24 API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Flightradar24 API use?

The Flightradar24 API uses HTTP bearer tokens issued from your fr24api.flightradar24.com account. Through Jentic the token is held in the encrypted vault and injected into the Authorization header at execution time.

How far back does Flightradar24 historical data go?

Historical flight positions, summaries, tracks, and events are available from May 11, 2016 onward. Queries for earlier dates return no records.

Can I get the live position of a specific flight?

Yes. Call /api/live/flight-positions/full or /api/live/flight-positions/light with filters such as callsign or registration to return the live record for that aircraft.

What are the rate limits for the Flightradar24 API?

Quotas are tied to your Flightradar24 plan rather than a fixed global limit. Use /api/usage to monitor remaining credits and watch for 429 responses with Retry-After headers.

How do I track a live flight through Jentic?

Search Jentic for 'track a live flight', load the schema for /api/live/flight-positions/full, and execute the call with the flight identifier. Install with pip install jentic and run it through Jentic One, the self-hosted execution layer.

What is the difference between the light and full variants?

Light variants return a compact payload optimised for map overlays and high-volume polling. Full variants return the same records with airline, aircraft type, registration, and route detail attached.

Can I limit what my agent is allowed to do with the Flightradar24 API?

Yes. Because you run Jentic One yourself, your own rules decide which of the 16 read-only Flightradar24 operations the agent may call and which credentials it may use. You can allow just the ones a task needs, such as live flight positions or flight summaries, and leave the rest, like historic flight events, airline lookups, or the account usage endpoint, out of the allowed set. Since these are all read-only tracking and metadata queries with parameters in the query string, scoping the operation list is what controls what the agent can reach.