Flightradar24 Search Scraper

What does Flightradar24 Search Scraper do?

Flightradar24 Search Scraper searches flights, airlines, airports, and aircraft registrations by free text — e.g. garuda, GA104, PK-GFA, singapore — and pushes one dataset row per real result.

It talks directly to the same internal REST API the official Flightradar24 Android app uses (mobile.flightradar24.com), the same one exposed by Flightradar24 All-in-One API. This Actor is the /search slice of that Actor, split out on its own. No account, no API key.

Why use this Actor?

• One free-text box, five categories — matches airlines/operators, airports, live flights, scheduled flights, and aircraft registrations in a single call
• Chainable ids — a live result's id (a hex string, e.g. "416f4471") can be looked up with Flightradar24 All-in-One API's /flight-lookup; an airport result's id (e.g. "SIN") can be looked up with its /airport* endpoints
• No account needed — every request is anonymous
• Use cases: flight-status lookup tools, airline/airport autocomplete, aviation research, building a flight id from a free-text search box

Input

Field	Type	Default	Description
query	string	—	Required. Flight number, callsign, registration, airline, or airport name/code.
limit	integer	25	Max results returned.

Example:

{
    "query": "garuda",
    "limit": 15
}

Output

Flightradar24's /v1/search/web/find response is { results: [...], info: {...}, stats: {...} } — a single flat results array, not split into separate arrays per category. Each entry already carries its own real type field (operator, airport, live, schedule, or aircraft), which this Actor uses as-is to tag the category — one dataset row per entry, untouched.

Real example (query "GIA1", trimmed):

[
    {
        "id": "GIA",
        "label": "Garuda Indonesia (GIA / GA)",
        "type": "operator",
        "match": "icao",
        "name": "Garuda Indonesia",
        "detail": {
            "operator_id": 203,
            "iata": "GA",
            "logo": "https://cdn.flightradar24.com/assets/airlines/logotypes/203.png"
        }
    },
    {
        "id": "416f4471",
        "label": "GA104 / GIA104 / B738 (PK-GNC)",
        "type": "live",
        "match": "begins",
        "detail": {
            "lat": -3.3,
            "lon": 104.8,
            "schd_from": "CGK",
            "schd_to": "PLM",
            "reg": "PK-GNC",
            "flight": "GA104"
        }
    },
    {
        "id": "GA101",
        "label": "GA101 / GIA101",
        "type": "schedule",
        "match": "begins",
        "detail": { "callsign": "GIA101", "flight": "GA101", "operator": "GIA", "operator_id": 203 }
    }
]

Known limitations

• Not paginated. Flightradar24's /search endpoint takes a single limit and returns one page — there is no page/cursor parameter to iterate further. limit is the only control this Actor exposes.
• Flight detail, airport boards, and bulk reference dumps are separate endpoints on the parent — this Actor is search-only. Use Flightradar24 All-in-One API for /flight-lookup, /airport*, /airlines, /airports, and the live gRPC feed.

Pricing

This Actor uses Pay Per Event billing: charged $0.002 per result row pushed to the dataset (event result, FREE tier price — lower on paid plans). See the Actor's Pricing tab for current rates.