Kayak APIkayak.com ↗
Access Kayak flight price calendars (~300 days), nearby airport lookups, and popular destination suggestions via a simple REST API.
What is the Kayak API?
The Kayak API exposes 3 endpoints covering flight price prediction calendars, nearby airport discovery, and popular destination lookups. The get_price_calendar endpoint returns up to ~300 days of average prices for any origin-destination pair, with each date tagged by a color-coded price level (green, orange, or red) so developers can quickly surface the cheapest travel windows without parsing raw fare data.
curl -X GET 'https://api.parse.bot/scraper/4e57f69c-c489-4b22-9b45-5f4d0c360e05/get_price_calendar?origin=WAS&trip_type=roundTrip&destination=LAX' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace kayak-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Kayak Flight Data SDK — bounded, re-runnable; every call capped."""
from parse_apis.kayak_flight_data_api import Kayak, TripType, PriceLevel, RouteNotFound
client = Kayak()
# Get a price calendar for a route — full ~300-day forecast in one call.
calendar = client.pricecalendars.get(origin="WAS", destination="LAX", trip_type=TripType.ROUND_TRIP)
print(f"Route: {calendar.origin} → {calendar.destination}, {calendar.total_dates} days forecasted")
# Inspect the cheapest predictions (green = cheap).
green_days = [p for p in calendar.predictions if p.price_level == PriceLevel.GREEN]
if green_days:
cheapest = min(green_days, key=lambda p: p.avg_price)
print(f"Cheapest green day: {cheapest.date} at ${cheapest.avg_price:.2f}")
# Construct an airport and list nearby alternatives.
lax = client.airport(code="LAX")
for apt in lax.nearby(limit=3):
print(f"Nearby: {apt.display_name} — {apt.distance_miles} mi, popularity {apt.popularity}")
# List popular destinations from an origin airport.
jfk = client.airport(code="JFK")
for dest in jfk.destinations(limit=3):
print(f"Destination: {dest.city} ({dest.airport_code}), {dest.country}")
# Typed error handling for an invalid route.
try:
client.pricecalendars.get(origin="ZZZ", destination="QQQ")
except RouteNotFound as exc:
print(f"Route not found: {exc}")
print("exercised: pricecalendars.get / airport.nearby / airport.destinations / RouteNotFound")
Get flight price prediction calendar for a route. Returns approximately 300 days of average prices with color-coded price levels (green=cheap, orange=moderate, red=expensive) to help find the cheapest travel dates. Pagination is not applicable; the full calendar is returned in a single response.
| Param | Type | Description |
|---|---|---|
| originrequired | string | Origin airport or city code (e.g., WAS, JFK, LAX) |
| trip_type | string | Trip type: 'roundTrip' or 'oneWay' |
| destinationrequired | string | Destination airport or city code (e.g., LAX, MIA, LHR) |
{
"type": "object",
"fields": {
"origin": "string - origin airport code",
"currency": "string - currency code for prices",
"trip_type": "string - trip type used for the query",
"destination": "string - destination airport code",
"predictions": "array of objects with date, avg_price, and price_level (green/orange/red)",
"total_dates": "integer - number of dates with predictions"
},
"sample": {
"data": {
"origin": "WAS",
"currency": "USD",
"trip_type": "roundTrip",
"destination": "LAX",
"predictions": [
{
"date": "2026-06-10",
"avg_price": 401.61,
"price_level": "orange"
},
{
"date": "2026-06-11",
"avg_price": 399.41,
"price_level": "orange"
},
{
"date": "2026-06-12",
"avg_price": 396.12,
"price_level": "orange"
}
],
"total_dates": 301
},
"status": "success"
}
}About the Kayak API
Price Calendar
The get_price_calendar endpoint accepts an origin and destination airport or city code (e.g., JFK, LHR) along with an optional trip_type of roundTrip or oneWay. It returns a predictions array where each object contains a date, an avg_price in the response's currency, and a price_level string — green for cheap dates, orange for moderate, and red for expensive. The total_dates field tells you exactly how many forecast dates are included, typically around 300.
Nearby Airports
The get_nearby_airports endpoint takes a single code parameter and returns an airports array. Each airport object includes code, name, city, display_name, full_display, distance_miles, popularity, and an is_nearby boolean. The total field gives the count of results. This is useful for building flexible search UIs where travelers might consider flying into or out of an alternative hub to save money.
Popular Destinations
The get_destinations endpoint accepts an origin airport code and an optional limit (up to 50). It returns a destinations array where each item includes airport_code, display_name, city, country, country_code, region, latitude, and longitude. The total field reflects the number of results returned. Geographic coordinates let you plot destinations on a map or calculate distances client-side.
The Kayak API is a managed, monitored endpoint for kayak.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when kayak.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official kayak.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a fare calendar widget that highlights the cheapest departure dates using
price_levelcolor codes. - Suggest alternative departure airports to users based on
distance_milesfrom their primary airport. - Power a destination discovery feature showing popular routes from any origin with geographic coordinates for map rendering.
- Alert users via a price-tracking tool when
avg_pricefor a given date drops to agreenprice level. - Generate flexible date travel recommendations by scanning ~300 days of
predictionsfor low-cost windows. - Pre-populate airport search dropdowns with nearby alternatives ranked by
popularity.
| 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 | 100 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 have an official developer API?+
What does `price_level` in the price calendar mean, and how granular is the pricing data?+
predictions array carries a price_level of green (cheap), orange (moderate), or red (expensive), alongside an avg_price numeric value in the currency returned by the query. The data covers approximately 300 future dates per route. Prices are averages, not guaranteed fares, and do not include a breakdown by airline or cabin class.Does the API return live fare quotes or bookable itineraries?+
get_price_calendar, airport proximity data via get_nearby_airports, and destination metadata via get_destinations. You can fork this API on Parse and revise it to add an endpoint targeting real-time fare search results.Can I filter the price calendar by airline or number of stops?+
get_price_calendar endpoint does not expose airline, stop count, or flight duration filters. Inputs are limited to origin, destination, and trip_type. You can fork the API on Parse and revise it to add stop-count or carrier filtering if those fields become available in the source data.How fresh is the price calendar data?+
predictions objects indicating when a specific average was computed.