Booking Flights Scraper

What does Booking.com Flights Scraper do?

Booking.com Flights Scraper searches Booking.com flights round-trip or one-way, with real airline/price/duration data — confirmed live: a real Bangkok-Singapore search returned 956 real results. Free-text origins/destinations are resolved to Booking's internal location id format automatically. Optionally fetches full baggage-policy/fare-rule detail for every offer in one run. Also works as a standalone airport/city lookup.

It talks directly to the same internal API the official Booking.com Android app uses, reverse-engineered by capturing live traffic from a real device — flights is a genuinely separate backend from hotels, confirmed live by opening the app's own Flights tab. No Booking.com account, no API key of your own. This is the flights slice of Booking.com All-in-One API, split out as its own focused Actor.

Why use Booking.com Flights Scraper?

• Real results, confirmed live — 956 real flights with real airline/price/duration data for a real Bangkok-Singapore search
• Real multi-region pricing — the same search with a different currency returns genuinely different prices, not a symbol swap
• Automatic location resolution — pass plain city/airport names; this Actor resolves them to Booking's internal id format for you
• Optional full fare-rule detail in the same run — baggage policy and fare rules, no separate Actor call needed
• No account needed — every request works fully anonymously
• Use cases: flight price monitoring, travel search products, fare-rule comparison

Input

Field	Type	Description
locationQuery	string	If set, this Actor only looks up matching airports/cities and pushes them — no flight search. Leave empty to search flights.
locationType	string	from | to. Narrows locationQuery suggestions by leg.
from / to	string	Exact resolved id, e.g. BKK.AIRPORT / SIN.CITY. Skips resolution.
fromQuery / toQuery	string	Free-text origin/destination, e.g. Bangkok. Resolved automatically (first match). Ignored if from/to is set.
departDate	string (date)	YYYY-MM-DD. Required for a flight search.
returnDate	string (date)	YYYY-MM-DD. Omit for a one-way search.
adults	integer	Default 1
cabinClass	string	ECONOMY | PREMIUM_ECONOMY | BUSINESS | FIRST
sort	string	BEST | CHEAPEST | FASTEST
page	integer	Default 1
currency	string	Confirmed live to change returned prices.
includeDetail	boolean	Fetch full baggage-policy/fare-rule detail per offer. Default false.
maxItems	integer	Stop once this many offers have been pushed. Default: push every result from the search.

Example (search):

{
    "fromQuery": "Bangkok",
    "toQuery": "Singapore",
    "departDate": "2026-09-19",
    "returnDate": "2026-09-26",
    "currency": "USD",
    "maxItems": 20
}

Example (location lookup only):

{ "locationQuery": "Bangkok", "locationType": "from" }

Output

One dataset row per flight offer (trimmed example):

{
    "token": "d6a1f_H4sIAAAAAAAA...",
    "segments": [
        {
            "departureAirport": { "code": "BKK", "name": "Suvarnabhumi Airport" },
            "arrivalAirport": { "code": "SIN", "name": "Changi Airport" },
            "departureTime": "2026-09-20T10:55:00"
        }
    ],
    "detail": { "...": "full baggage policy/fare rules, only present when includeDetail is true" }
}

Known limitations

• Location resolution takes the first autocomplete match. For an ambiguous fromQuery/toQuery, run a locationQuery lookup first and pass the exact from/to id instead.
• No cross-search pagination beyond page. This mirrors the parent Actor's own /flights?page= parameter — there's no cursor/offset scheme beyond it.
• This is an unofficial, reverse-engineered integration, not affiliated with or endorsed by Booking.com B.V. Behavior may change if Booking.com changes its API.

Pricing

Pay-per-event: $0.0025 per flight result (FREE plan; BRONZE/SILVER/GOLD/PLATINUM/DIAMOND get automatic discounts based on your Apify plan). Location suggestion lookups are not charged.