Flightradar24 Reference Data Scraper

What does Flightradar24 Reference Data Scraper do?

Flightradar24 Reference Data Scraper dumps Flightradar24's bulk reference data — the full list of airlines (~2,700 rows) and/or airports (~6,700 rows) — from the same internal REST API the official Flightradar24 Android app uses, one dataset row per entry. No API key, no login, no scraping setup.

Why use this Actor?

• Complete reference tables in one run — every airline or airport Flightradar24 knows about, not a paginated subset
• No login, no API key — talks to the same anonymous mobile.flightradar24.com endpoints the app itself uses
• Split from a bigger Actor — this is a narrow spin-off of flightradar24-all-in-one-api, which exposes the full live-tracking + search API surface. Use this Actor if all you need is the bulk airline/airport lookup tables; use the all-in-one Actor for live flights, search, and airport boards.

Input

Field	Type	Default	Description
datasets	array of "airlines" | "airports"	both	Which bulk reference dumps to fetch. Leave empty to fetch both.

Example input to fetch airlines only:

{ "datasets": ["airlines"] }

Output

One dataset item per airline or airport, tagged with a dataset field so both kinds can share one dataset. Rows are pushed in batches of 500 to stay well under Apify's per-call dataset push limits.

Airline row:

{
    "dataset": "airlines",
    "active": true,
    "hub": null,
    "iata": "2I",
    "icao": "CSB",
    "id": 1545,
    "metadata": {
        "images": {
            "logotypes": {
                "default": { "file": { "source": "https://cdn.flightradar24.com/assets/airlines/logotypes/1545.png" } }
            }
        }
    },
    "modified": 1737980180,
    "name": "21 Air",
    "photoId": null,
    "url": "2i-csb"
}

Airport row:

{
    "dataset": "airports",
    "id": 1900,
    "name": "A Coruna Airport",
    "iata": "LCG",
    "icao": "LECO",
    "city": "A Coruna",
    "lat": 43.302059,
    "lon": -8.37725,
    "country": "Spain",
    "alt": 326,
    "size": 4352,
    "timezone": { "name": "Europe/Madrid", "offset": 7200, "offsetHours": "2:00", "abbr": "CEST", "isDst": true },
    "countryId": 209,
    "videoStream": null
}

Both endpoints return their rows nested under a { version, rows: [...] } wrapper server-side — this Actor unwraps rows and pushes each entry as its own dataset item.

Pricing

This Actor uses Pay Per Event billing: charged $0.002 per row returned (event reference-record, FREE tier price — lower on paid plans), not per run. Requesting both datasets returns several thousand results in a single run (roughly 2,700 airline rows + 6,700 airport rows), so factor that into expected cost before running with default input.

Known limitations

• These are large, close-to-static reference dumps. Flightradar24 updates them occasionally (new airlines, airport metadata changes) but not in real time — cache the result client-side rather than re-running this Actor on every request, per the parent Actor's own guidance.
• Row counts are Flightradar24's own current data, not a number guaranteed by this Actor — expect roughly 2,700 airlines and 6,700 airports, but the exact count will drift over time as Flightradar24 adds or removes entries.
• Field shapes are undocumented by Flightradar24 and were determined empirically by inspecting live responses — a future change on Flightradar24's side could add, remove, or rename fields without notice.

FAQ

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

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.