# Flightradar24 All-in-One API (`romy/flightradar24-all-in-one-api`) Actor

Real-time, unofficial Flightradar24 API — live flight positions by bounding box, flight detail, live tracking, historical playback, nearest-flights, search, and airport arrival/departure boards. No API key, no login, no scraping setup.

- **URL**: https://apify.com/romy/flightradar24-all-in-one-api.md
- **Developed by:** [Romy](https://apify.com/romy) (community)
- **Categories:** Travel, Developer tools
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $31.20 / 1,000 live feeds

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### What does Flightradar24 All-in-One API do?

**Flightradar24 All-in-One API** is a unified REST endpoint for Flightradar24's live flight-tracking data — live positions by bounding box, most-tracked flights globally, full flight detail, live position streaming, historical playback, batch status, search, and airport arrival/departure/on-ground boards — all from a single always-on API powered by [Apify Standby](https://docs.apify.com/platform/actors/development/programming-interface/standby).

It talks directly to the same two internal APIs the official [Flightradar24](https://www.flightradar24.com/) Android app uses — the gRPC live feed (`data-feed.flightradar24.com`) and the legacy REST API (`mobile.flightradar24.com`) — reverse-engineered by static decompilation and validated against real live traffic. No API key, no login, no scraping setup — call the endpoint, get JSON back instantly.

### Why use Flightradar24 All-in-One API?

- **All Flightradar24 data in one place** — live map, top flights, flight detail, live tracking, playback, search, and airport boards in one API
- **Always-on** — Standby mode means no cold start, responds in milliseconds
- **Standard REST + NDJSON streaming** — works with any language: curl, Python, JavaScript, Postman
- **Use cases:** aviation monitoring, airport operations dashboards, logistics/cargo tracking, flight-delay research, competitive intelligence on airline route activity

### Endpoints

**Feed** (gRPC-backed, live tracking):

| Method | Path | Description |
|--------|------|-------------|
| `GET` | `/live-feed` | Live flights within a bounding box |
| `GET` | `/top-flights` | Most-tracked flights globally right now |
| `GET` | `/flight-details` | Full detail for one flight — aircraft, schedule, progress, trail |
| `GET` | `/follow-flight` | Stream live position updates for one flight (NDJSON) |
| `GET` | `/playback` | Historical flight positions at a past point in time |
| `GET` | `/flights-status` | Batch position/status refresh for a list of known flight ids |
| `GET` | `/nearest-flights` | Flights nearest to a coordinate, sorted by distance |

**Legacy REST** (search & airport data):

| Method | Path | Description |
|--------|------|-------------|
| `GET` | `/search` | Search flights, airlines, airports, or registrations |
| `GET` | `/flight-lookup` | Flight detail by hex id, optionally at a past point in time |
| `GET` | `/airport` | Airport info — location, weather, stats, photos |
| `GET` | `/airport/arrivals` | Arrival board for an airport |
| `GET` | `/airport/departures` | Departure board for an airport |
| `GET` | `/airport/on-ground` | Aircraft currently on the ground at an airport |
| `GET` | `/airport/disruptions` | Airports currently experiencing delays, ranked |
| `GET` | `/airlines` | Bulk airline reference dump (~2,700 rows) |
| `GET` | `/airports` | Bulk airport reference dump (~6,700 rows) |

### How to use

1. Go to [Apify Store](https://apify.com/romy/flightradar24-all-in-one-api) and click **Try for free**
2. The actor runs in Standby mode — it starts once and stays alive
3. Call the API using your Apify token:

```bash
curl "https://romy--flightradar24-all-in-one-api.apify.actor/live-feed?north=6&south=-11&west=95&east=141&limit=50" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN"
```

**Quick tip:** To get all flights over Indonesia, use `north=6&south=-11&west=95&east=141`.

### Input (Query Parameters)

#### GET `/live-feed`

| Param | Type | Default | Description |
|-------|------|---------|-------------|
| `north` / `south` / `west` / `east` | number | required | Bounding box in decimal degrees |
| `limit` | integer | 1500 | Max flights to return |
| `maxage` | integer | 14400 | Max age (seconds) of position data to include |

#### GET `/top-flights`

| Param | Type | Default | Description |
|-------|------|---------|-------------|
| `limit` | integer | 50 | Max entries to return |

#### GET `/flight-details`

| Param | Type | Default | Description |
|-------|------|---------|-------------|
| `flight_id` | integer | required | From a `/live-feed`, `/top-flights`, or `/playback` result |

#### GET `/follow-flight`

| Param | Type | Default | Description |
|-------|------|---------|-------------|
| `flight_id` | integer | required | From a `/live-feed`, `/top-flights`, or `/playback` result |
| `duration` | integer | 30 | Seconds to keep the stream open (max 120) |

Response is `application/x-ndjson` — one JSON object per line, one line per position update pushed by Flightradar24 (roughly every 1–3 seconds while airborne):

```bash
curl -N "https://romy--flightradar24-all-in-one-api.apify.actor/follow-flight?flight_id=1094013202&duration=60" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN"
```

#### GET `/playback`

| Param | Type | Default | Description |
|-------|------|---------|-------------|
| `north` / `south` / `west` / `east` | number | required | Bounding box in decimal degrees |
| `timestamp` | integer | required | Unix timestamp (seconds) of the point in time to look up |
| `limit` | integer | 1500 | Max flights to return |

Depth is the last **7 days** — this matches the free tier of the Flightradar24 app itself (older timestamps return an empty flight list rather than an error; it's enforced server-side by Flightradar24, not by this Actor).

#### GET `/flights-status`

| Param | Type | Default | Description |
|-------|------|---------|-------------|
| `flight_ids` | string | required | Comma-separated flight ids, e.g. `1094013202,1094013408` |

Cheaper than calling `/flight-details` once per flight when you already have the ids (e.g. from `/live-feed` or `/airport/on-ground`) and only need a fresh position/status.

#### GET `/nearest-flights`

| Param | Type | Default | Description |
|-------|------|---------|-------------|
| `lat` / `lon` | number | required | Center coordinate |
| `radius` | integer | 200000 | Search radius in meters |
| `limit` | integer | 300 | Max results |

Powers the app's own "Search > Nearby" screen — results are sorted nearest-first with a `distance` (meters) on each entry. This is a real server-side nearest-neighbor query, unlike the app's AR "point at the sky" view, which just calls `/live-feed` with a tight bounding box instead.

#### GET `/search`

| Param | Type | Default | Description |
|-------|------|---------|-------------|
| `query` | string | required | Flight number, callsign, registration, airline, or airport name/code |
| `limit` | integer | 25 | Max results |

Live-flight results include a hex `id` (e.g. `"41336b86"`) — pass it to `/flight-lookup`. Airport results include a numeric `id` — pass it to `/airport*`.

#### GET `/flight-lookup`

| Param | Type | Default | Description |
|-------|------|---------|-------------|
| `flight` | string | required | Hex flight id from a `/search` result |
| `history` | integer | — | Unix timestamp (seconds) — look up this flight's state at a past point in time instead of now |

This is the REST equivalent of `/flight-details`, and also covers flights the gRPC feed itself won't return — already-landed aircraft, ground vehicles, anything not currently broadcasting a live position.

#### GET `/airport`

| Param | Type | Default | Description |
|-------|------|---------|-------------|
| `id` | string | required | Airport id, from a `/search` result (e.g. `631` for Jakarta CGK) |
| `include` | string | `images,weather,stats,runways` | Sections to include |

#### GET `/airport/arrivals`, `/airport/departures`, `/airport/on-ground`

| Param | Type | Default | Description |
|-------|------|---------|-------------|
| `id` | string | required | Airport id |
| `page` | integer | 1 | Page number (100 results per page — Flightradar24's server rejects any other page size) |

#### GET `/airport/disruptions`

| Param | Type | Default | Description |
|-------|------|---------|-------------|
| `continent` | integer | 0 | 0 = all continents |
| `period` | string | `live` | |
| `type` | string | `both` | |

### Output Example

`/live-feed`:

```json
{
  "success": true,
  "flights": [
    {
      "flightId": 1094013202,
      "lat": -5.815,
      "lon": 111.413,
      "track": 205,
      "alt": 38000,
      "speed": 476,
      "callsign": "PAS646",
      "onGround": false,
      "timestampMs": "1786924707066",
      "extraInfo": { "flight": "IP646", "reg": "PK-PWO", "type": "A320" }
    }
  ]
}
```

`/flight-details`:

```json
{
  "success": true,
  "aircraftInfo": { "reg": "PK-PWO", "type": "A320", "fullDescription": "Airbus A320-214", "registeredOwners": "Pelita Air" },
  "scheduleInfo": { "flightNumber": "IP646", "scheduledDeparture": "1786921200", "actualDeparture": "1786921125" },
  "flightProgress": { "progressPct": 65, "flightStage": 3, "delayStatus": 1 },
  "flightTrail": [ { "snapshotId": "1786921371", "lat": -1.34, "lon": 116.72, "altitude": 6175, "spd": 272 } ]
}
```

`/flights-status`:

```json
{
  "success": true,
  "flights": {
    "1094013202": { "lat": -5.82, "lon": 111.41, "status": 4, "timestamp": "1786924711" }
  }
}
```

### Pricing

This Actor uses **Pay Per Event** billing — you only pay for successful API calls (failed 4xx/5xx requests are not charged). `/follow-flight` is billed per update received, not per request, since one call can stay open for up to 120 seconds and deliver dozens of updates.

### Known limitations

- **All eight of the feed's gRPC methods are now confirmed and exposed.** The last two to fall into place — `/nearest-flights` and `/flights-status` — took longer to trigger than the rest (the app's own AR "flights near me" camera view turned out to be a red herring, reusing `/live-feed` instead). `/flights-status` was found via an airport's "on ground" tab; `/nearest-flights` needed the "while using the app" foreground location permission specifically — granting only the AR view's camera/location prompt isn't enough.
- **Some `aircraftInfo` fields are paywalled by Flightradar24 itself, not by this Actor.** `msn` (serial number), `acAge`/`acBirthDate`, and `countryOfReg` come back empty even though their companion `msnAvailable` / `ageAvailable` / `isCountryOfRegAvailable` flags report `true` (confirmed server-side gating, not a UI-only lock — verified against both an anonymous session and a modified client that locally fakes a paid subscription, with identical results either way) — this API calls the feed anonymously, the same way the free tier of the app does, and there's no way to unlock those fields short of an actual paying Flightradar24 account.
- **`/playback` depth is 7 days**, matching the app's own free-tier limit.
- **`/airport/arrivals`, `/airport/departures`, `/airport/on-ground` only accept 100 results per page.** Flightradar24's server validates `limit` against a fixed allow-list rather than an arbitrary range — 10/25/50/200 all get rejected with HTTP 422, only 100 works — so this Actor hardcodes it and exposes `page` for pagination instead.
- **`/airlines` and `/airports` are large, close-to-static reference dumps** (thousands of rows) — cache the result client-side rather than calling on every request.

### FAQ

**Does this require a Flightradar24 account?**
No. The Actor uses the same anonymous data/search feed the Flightradar24 mobile app uses — no login, no API key.

**Is the data real-time?**
Yes — positions update roughly every 1–3 seconds per flight. `/live-feed` is a snapshot; `/follow-flight` streams continuous updates for one flight.

**Is this official?**
No. This is an independent tool using Flightradar24's internal APIs, reverse-engineered from the public Android app. Use responsibly and in accordance with Flightradar24's Terms of Service.

**Need a custom integration?**
Contact me at romysaputrasihanandaa@gmail.com or [hire me on Fiverr](https://www.fiverr.com/romyssss).

# Actor input Schema

## Actor input object example

```json
{}
```

# Actor output Schema

## `api` (type: `string`):

This Actor doesn't write to a dataset — every response is returned directly over HTTP by its Standby web server. See the README / web server OpenAPI schema (webServerSchema) for the full endpoint list and response shapes (GET /live-feed, /top-flights, /flight-details, /follow-flight, /playback, /flights-status, /nearest-flights, /search, /flight-lookup, /airport, /airport/arrivals, /airport/departures, /airport/on-ground, /airport/disruptions, /airlines, /airports).

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("romy/flightradar24-all-in-one-api").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("romy/flightradar24-all-in-one-api").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call romy/flightradar24-all-in-one-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,romy/flightradar24-all-in-one-api"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/EanSbRSKJi8ZwKdWv/builds/FOPrXWKlRHFRi9K0d/openapi.json