Planefinder Myflight Search Scraper

What does Planefinder MyFlight Search Scraper do?

Planefinder MyFlight Search Scraper searches flight schedules from Planefinder's "MyFlight" API — either by carrier + flight number + date, or by departure/arrival airport route + date. Returns real-time schedule/status data (scheduled, estimated, and actual times; terminal/gate) for the matching flight instance(s).

Unlike Planefinder's flight-tracking features, this endpoint does not require an account or device token.

Results are pushed directly to an Apify dataset.

Why use Planefinder MyFlight Search Scraper?

• Trip planning / flight status lookup — check a specific flight's schedule and current status.
• Route timetable discovery — find every flight number operating a given route on a given date.
• Delay monitoring — poll dep_est_ts/dep_act_ts vs dep_schd_ts over time to track delays.

How to use Planefinder MyFlight Search Scraper

1. Open the Actor and click Try for free.
2. In the Input tab, provide flight_queries and/or route_queries.
3. Click Start and wait for the run to finish.
4. Download results from the Output tab in JSON, CSV, or Excel format.

Input

At least one of flight_queries or route_queries must be provided.

Field	Type	Description
flight_queries	array of objects	Each needs carrier, flightNumber, date (YYYY-MM-DD)
route_queries	array of objects	Each needs departureAirport, arrivalAirport (IATA codes), date (YYYY-MM-DD)
max_results_per_query	integer	Max flights kept per query (default 50, max 200). Caps cost on busy routes.

{
    "flight_queries": [
        { "carrier": "GA", "flightNumber": "401", "date": "2026-07-27" }
    ],
    "route_queries": [
        { "departureAirport": "CGK", "arrivalAirport": "DPS", "date": "2026-07-27" }
    ]
}

Output

Each item represents one flight instance.

{
    "query_type": "flight_number",
    "dep_apt": "DPS",
    "arr_apt": "CGK",
    "dep_timezone_id": "Asia/Makassar",
    "arr_timezone_id": "Asia/Jakarta",
    "carrier": "GA",
    "flight_number": 401,
    "reg": null,
    "aircraft_type": "738",
    "dep_schd_ts": 1785105000,
    "dep_est_ts": null,
    "dep_act_ts": null,
    "dep_terminal": "D",
    "arr_schd_ts": 1785112200,
    "arr_terminal": "3",
    "last_updated_ts": 1785046737
}

Data table

Field	Description
query_type	flight_number or route, depending on which query produced this result
dep_apt / arr_apt / divert_apt	Route airports (IATA)
carrier / flight_number	The operating flight number
reg / aircraft_type	Aircraft registration and type, if known ahead of departure
dep_schd_ts / dep_est_ts / dep_act_ts / dep_airborne_ts	Scheduled/estimated/actual/airborne departure Unix timestamps
arr_schd_ts / arr_est_ts / arr_act_ts / arr_touchdown_ts	Scheduled/estimated/actual/touchdown arrival Unix timestamps
dep_terminal / dep_gate / arr_terminal / arr_gate / arr_baggage_claim	Airport logistics fields, if published
last_updated_ts	When Planefinder last refreshed this record

Tips

• Fields are frequently null for flights far in the future (gate/terminal/estimated times are usually only published close to departure).
• Combine flight_queries and route_queries in the same run — each result includes query_type so you can trace which input produced it.

Pricing

This Actor uses the Pay Per Event model: $0.03 per result in the dataset (plus a negligible one-time actor-start fee). flight_queries typically return one result each. route_queries can return dozens of scheduled flights per airport pair per day — results are capped by max_results_per_query (default 50) to keep a single query's cost predictable.

FAQ and support

This Actor uses Planefinder's public mobile API for informational purposes only. Do not use the data for commercial redistribution without verifying Planefinder's terms of service.

For bugs or feature requests, open an issue on the Actor's Issues tab. Custom scraping solutions are available on request.