Flightradar24 Flight Detail Scraper

What does Flightradar24 Flight Detail Scraper do?

Flightradar24 Flight Detail Scraper takes one or more numeric Flightradar24 flight ids and pushes, for each one, in a single merged dataset row:

• Full flight detail (aircraft, schedule, progress, flight trail) via the internal gRPC live feed
• A REST lookup by hex-converted id — covers flights the gRPC feed itself won't return (already-landed aircraft, ground traffic not currently broadcasting)
• A batched live-status refresh (position, squawk, status) fetched once for all input ids together

Why use Flightradar24 Flight Detail Scraper?

• Three calls, one row — gRPC detail, REST lookup, and live status merged per flight id, with the batch status call made once regardless of how many ids you pass
• No API key, no login — same anonymous access the official Flightradar24 Android app uses
• Use cases: enriching a list of flight ids from a live-feed/top-flights query, tracking dashboards, delay/status monitoring, flight-detail lookups for logistics or research

How it connects to the parent Actor

This is the flight-detail slice of Flightradar24 All-in-One API, split out as its own focused Actor. The parent exposes the full internal gRPC feed (data-feed.flightradar24.com) and legacy REST API (mobile.flightradar24.com) as an always-on Standby API with many more endpoints (live-feed by bounding box, search, airport boards, streaming, playback, nearest-flights). This Actor covers only /flight-details, /flight-lookup, and /flights-status, run per input flight id.

Input

Field	Type	Description
flightIds	integer[]	Numeric Flightradar24 flight ids. Optional: leave empty and flightCount (default 1) currently airborne flights are picked from the live feed.
flightCount	integer	How many flights to auto-pick when flightIds is empty (1-20, default 1).
includeLookup	boolean	Also fetch each flight via the legacy REST /clickhandler lookup. Default true.
includeStatus	boolean	Also fetch a batched live-status refresh for all input ids in one call. Default true.
historyUnixSeconds	integer	Optional. Passed to every REST lookup call — looks up each flight's state at a past point in time.

Example:

{
    "flightIds": [1094013202],
    "includeLookup": true,
    "includeStatus": true
}

Output

One dataset row per flight id:

{
    "flightId": 1094013202,
    "flightIdHex": "41355112",
    "details": {
        "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 }]
    },
    "lookup": {
        "identification": { "id": "41355112", "number": { "default": "IP646" } },
        "aircraft": { "registration": "PK-PWO", "model": { "text": "Airbus A320-214" } }
    },
    "status": { "lat": -5.82, "lon": 111.41, "status": 4, "timestamp": "1786924711" }
}

lookup and status are omitted (undefined) when includeLookup / includeStatus are set to false.

Known limitations

• The hex-conversion technique for /flight-lookup ((flightId >>> 0).toString(16)) is inferred from a source comment in the parent Actor's own REST client — "the hex flight id can come from a gRPC Flight.flightId converted to hex" — not from any documented Flightradar24 API. It matches the format of real hex ids returned by Flightradar24's own /search endpoint (e.g. "41336b86"), but Flightradar24 has not published this mapping.
• 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 *Available flags report true — this API calls the feed anonymously, the same way the free tier of the Flightradar24 app does.
• /flight-lookup's history depth is limited server-side by Flightradar24 (matches the app's own free-tier window), not by this Actor.
• Live-feed by bounding box, search, airport boards, streaming, and playback are covered by the parent Flightradar24 All-in-One API and its other spin-off Actors, not this one.

Pricing

This Actor uses Pay Per Event billing: charged $0.004 per flight id processed (event flight-detail, FREE tier price — lower on paid plans). See the Actor's Pricing tab for current rates.