kayak.com.hk APIkayak.com.hk ↗
Search one-way flights, multi-origin flexible-date fares, and monthly price calendars from kayak.com.hk via a structured JSON API.
curl -X GET 'https://api.parse.bot/scraper/b2498c0a-fe38-461b-a89a-4dedd037a506/search_flights?date=2026-06-01&cabin=Economy&limit=5&origin=LHR&destination=JFK' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for one-way flights between two airports. Returns flight options with pricing, schedules, and booking links sorted by best match.
| Param | Type | Description |
|---|---|---|
| daterequired | string | Departure date in YYYY-MM-DD format. |
| cabin | string | Cabin class. Accepted values: Economy, PremiumEconomy, Business, First. |
| limit | integer | Maximum number of flight results to return. |
| originrequired | string | Origin airport IATA code (e.g. HND, NRT, LAX). |
| destinationrequired | string | Destination airport IATA code (e.g. YVR, SFO, LHR). |
{
"type": "object",
"fields": {
"flights": "array of flight objects containing origin, destination, airline, price, currency, departure_time, arrival_time, departure_date, arrival_date, duration, stops, stop_locations, cabin_class, flight_number, booking_link"
},
"sample": {
"data": {
"flights": [
{
"price": "7,710",
"stops": 1,
"origin": "HND",
"airline": "Cathay Pacific",
"currency": "HKD",
"duration": "23h 0m",
"cabin_class": "Economy",
"destination": "YVR",
"arrival_date": "2026-06-01T21:50",
"arrival_time": "21:50",
"booking_link": "https://www.agoda.com/en-us/packages/book?cid=1930882&pk=...",
"flight_number": "527",
"departure_date": "2026-06-01T14:50",
"departure_time": "14:50",
"stop_locations": [
"Hong Kong"
]
}
]
},
"status": "success"
}
}About the kayak.com.hk API
The KAYAK Hong Kong API covers 3 endpoints for querying flight data from kayak.com.hk, returning airline names, prices, departure/arrival times, and booking links. The search_flights endpoint handles direct one-way route queries between two IATA airport codes, while get_price_calendar maps daily lowest fares across an entire month, making it practical to build fare-tracking tools or date-flexible travel search into an application.
Endpoints and What They Return
The search_flights endpoint accepts a required origin and destination IATA code pair plus a departure date in YYYY-MM-DD format. It returns an array of flight objects, each carrying airline, price, currency, departure_time, arrival_time, departure_date, and a destination field. An optional cabin parameter accepts Economy, PremiumEconomy, Business, or First; a limit parameter caps the number of results returned.
Flexible and Multi-Origin Search
search_flights_multi_origin accepts an optional destination IATA code, an optional target date, and a flex_days integer that broadens the search window by ±N days around that date. Omitting the date defaults to 30 days from today. The endpoint returns the five cheapest flights per origin airport across the matched date range — useful when the departure city is not fixed, such as regional arbitrage fare comparisons or travel deal aggregators covering multiple Asian hub airports.
Price Calendar
get_price_calendar takes an origin and destination IATA code and returns a calendar object that maps individual dates to their lowest available average fare and a color indicator (typically used for heat-map visualizations). The success boolean signals whether calendar data was available for the route. No date input is required — the endpoint returns the current month's data for the given route pair.
- Build a fare alert tool that monitors the
pricefield daily viasearch_flightsand notifies users when a threshold is crossed. - Render a monthly calendar heat-map using
get_price_calendarcolor and price data to help users pick the cheapest departure day. - Compare one-way fares across multiple Asian departure cities by calling
search_flights_multi_originwithflex_daysset to ±7 days. - Aggregate cheapest-per-origin fares for a travel deals newsletter using the top-5-per-origin results from
search_flights_multi_origin. - Filter business-class availability on specific routes by passing
cabin: Businesstosearch_flightsand surfacing the resulting prices. - Track route-level price trends over time by storing daily
get_price_calendarresponses and comparing average fares week over week.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does KAYAK offer an official developer API?+
What does `search_flights_multi_origin` return, and how does the `flex_days` parameter work?+
airline, price, currency, departure_time, and arrival_time. Setting flex_days to, say, 3 expands the search to check fares on the target date plus the 3 days before and after it. Omitting both date and flex_days targets a date 30 days from today with no flex window.Does the API cover round-trip or multi-city itineraries?+
search_flights searches a single one-way leg, search_flights_multi_origin returns one-way fares per origin, and get_price_calendar shows one-way lowest fares per day. You can fork this API on Parse and revise it to add a round-trip or multi-city endpoint.What does the `calendar` object from `get_price_calendar` look like, and are all dates always populated?+
calendar object is a date-keyed map (e.g. "2025-08-01": { "price": 420, "color": "green" }). Some dates may be missing if no fare data is available for that day on the route. The success boolean at the top level indicates whether the calendar response as a whole returned usable data.