Klook Airport Transfers Scraper

What does Klook Airport Transfers Scraper do?

Klook Airport Transfers Scraper looks up one or more flights for Klook airport transfer booking, one dataset row per flight.

It talks directly to the same internal API the official Klook Android app uses, reverse-engineered by disassembling the app's native request-signing library and validated against live traffic captured from a real device. No Klook account, no API key. This is the airport-transfers slice of Klook All-in-One API, split out as its own focused Actor.

Why use Klook Airport Transfers Scraper?

• A genuinely separate subsystem — confirmed live by the parent Actor to use the exact same signing scheme, but talking to a completely different backend (transferairportapisrv) from the activities API
• Proven to reach the real backend, not just a signed 200 — the parent Actor confirmed a deliberately-wrong flight number produces a real "flight not found" app error rather than a signature error, proving the request is genuinely processed
• No account needed — works fully anonymously

How it connects to the parent

This Actor is a narrow, batch-run spin-off of klook-all-in-one-api (an always-on Standby REST API exposing every Klook endpoint). It reuses the parent's exact, proven request-signing logic (klook-client.ts, copied verbatim) but only wraps /transport/airport-transfers/search, and runs as a normal input-in/dataset-out Actor instead of a Standby API.

Input

Field	Type	Description
flights	array	Required. Array of { flightNumber, departureDate, direction } objects. direction is "arrival" (default) or "departure".

Example:

{ "flights": [{ "flightNumber": "CX123", "departureDate": "2026-09-15", "direction": "arrival" }] }

Output

One dataset row per flight lookup. Real example (from the parent Actor's own live-confirmed capture of GET /transport/airport-transfers/search?flight_number=CX123&departure_date=2026-08-27):

{
    "flightNumber": "CX123",
    "departureDate": "2026-08-27",
    "direction": "arrival",
    "result": { "success": true, "results": { "result": { "found": false, "flights": null } } }
}

found: false is a legitimate, correctly-working response for a flight/date combination Klook has no data for — not an error.

Known limitations

• Requires Apify's RESIDENTIAL proxy group. Klook's edge blocks non-residential IPs with a DataDome bot-challenge page — confirmed directly from this development sandbox (a request byte-for-byte identical to a working one, sent without the proxy, came back as a DataDome JS-challenge HTML page, not JSON). All outbound requests route through Actor.createProxyConfiguration({ groups: ['RESIDENTIAL'] }).
• Local dev smoke testing outside the Apify platform needs "Proxy external access" enabled on the account. This Actor's code was verified to be a byte-for-byte match against the parent's already-published, working klook-client.ts, and the local smoke test run during development failed exactly at the proxy-URL-acquisition step (ProxyConfiguration: The "Proxy external access" feature isn't enabled for your account) — before any request to Klook was even attempted. That's an account-tier restriction on pulling a proxy URL from outside a real platform Actor run, not a defect in this code; once deployed and actually run on Apify's platform, proxy access works through the normal SDK path.
• This does not book anything — it only performs the flight lookup step that precedes booking an airport transfer in the app.
• This is an unofficial, reverse-engineered integration, not affiliated with or endorsed by Klook Travel Technology Limited.

Pricing

Pay per event. Charged $0.01 per flight-lookup (FREE tier) — one event per flight lookup pushed to the dataset. See the Actor's Pricing tab for rates across all tiers.