Cheapest Dates API
A month of fares, one request
Send a route and a month. Get back the lowest fare Google Flights shows for every departure date, and the cheapest one, in one call.
- A month, or any range up to 61 days
- One-way, or a round trip of 1 to 30 nights
- Billed as one request
Free tier on RapidAPI. No card to try.
curl -X POST "https://google-flights-live-api.p.rapidapi.com/api/google_flights/cheapest_dates/v1" \
-H "Content-Type: application/json" \
-H "x-rapidapi-host: google-flights-live-api.p.rapidapi.com" \
-H "x-rapidapi-key: $RAPIDAPI_KEY" \
-d '{"from_airport":"JFK","to_airport":"LAX","month":"2027-01","nights":7,"currency":"USD","adults":1}'Short answer
What the cheapest dates endpoint returns
POST /api/google_flights/cheapest_dates/v1 on google-flights-live-api.p.rapidapi.com (RapidAPI key) takes one airport a side and a month or a date range. It returns one row per departure date with Google Flights' lowest fare for it, the cheapest date, and when the prices were fetched. Prices are Google's calendar estimates, without airline or flight details.{
"from_airport": "JFK",
"to_airport": "LAX",
"month": "2027-01",
"nights": 7,
"currency": "USD",
"adults": 1
}{
"from_airport": "JFK",
"to_airport": "LAX",
"trip_type": "roundtrip",
"nights": 7,
"adults": 1,
"currency": "USD",
"fetched_at": "2026-11-17T09:06:07Z",
"dates_searched": 31,
"dates_with_price": 31,
"cheapest": {
"departure_date": "2027-01-06",
"return_date": "2027-01-13",
"price": 357
},
"dates": [
{
"departure_date": "2027-01-01",
"return_date": "2027-01-08",
"price": 457
},
{
"departure_date": "2027-01-02",
"return_date": "2027-01-09",
"price": 543
},
{
"departure_date": "2027-01-03",
"return_date": "2027-01-10",
"price": 525
},
{
"departure_date": "2027-01-04",
"return_date": "2027-01-11",
"price": 383
},
"…"
],
"source_note": "Prices are Google Flights' calendar estimates: the lowest fare Google shows for each date, for all passengers together, without airline or flight details. A full search for a date can return a different price; confirm the date you pick with the one-way or round-trip search before booking."
}| Field | Type | Meaning | In this run |
|---|---|---|---|
cheapest | object | The date with the lowest price in the range, with its return date on a round trip. | 2027-01-06 → 2027-01-13, $357 |
dates[].price | number | null | The lowest fare Google shows for that departure date, for all passengers together. Null where Google shows none. | $357 to $543 across the month |
dates_searched / dates_with_price | int | How many dates the range covered, and how many of them Google priced. | 31 / 31 |
fetched_at | string | When the calendar was read (UTC). Prices move; read them with this time. | 2026-11-17T09:06:07Z |
Pick a date here, then price it in full with the one-way or round-trip endpoint for flights, airlines and a booking link.
Request
Fields
Unknown fields are refused, so a typo never silently searches something else.
from_airport / to_airportstringOne IATA airport or city code a side, e.g. JFK.
monthstringYYYY-MM: every departure date of that month. A month already under way starts today. Send this, or the two range fields.
departure_date_from / departure_date_tostringYYYY-MM-DD, today or later, at most 61 days with both ends included.
nightsint 1–30A round trip of this many nights; each row then carries its return_date. Omit it for a one-way.
adultsint 1–9Defaults to 1. Prices are for all of them together.
currencystringe.g. USD, EUR.
{
"from_airport": "LHR",
"to_airport": "BCN",
"departure_date_from": "2027-02-01",
"departure_date_to": "2027-03-15",
"currency": "EUR"
}Errors
Every refusal is a 422 that names the field
Refused before anything is fetched. The body carries detail, help, hint and field, like every other 422 on this API.
| You sent | field | detail (example) |
|---|---|---|
| month and a date range together | month | month: send month or a date range, not both |
| month not YYYY-MM | month | month must be YYYY-MM (e.g. 2027-01), got '2027-1-5' |
| Neither month nor a range | departure_date_from | departure_date_from: required when month is not sent |
| A range over 61 days | departure_date_to | departure_date_to: the range is at most 61 days |
| A start date in the past | departure_date_from | departure_date_from: must be today or later in UTC |
| nights outside 1 to 30 | nights | nights: must be 1 to 30 |
| adults outside 1 to 9 | adults | adults: must be 1 to 9 |
Questions, answered plainly
- How many requests does it cost?
- One. A whole month (or any range up to 61 days) is one request on your RapidAPI plan, one-way or round trip, so PRO ($10 for 2,500 requests a month) covers 2,500 month-wide calendars.
- Is this a flight price calendar API?
- Yes. It returns the lowest fare Google Flights shows for each departure date (Google’s calendar estimates), one row per departure date with a null where Google shows none, plus the cheapest date of the range. Use it to pick the day, then price that day in full with the one-way or round-trip endpoint.
- Are these the same prices as a full search?
- They are Google Flights’ calendar estimates: the lowest fare Google shows for each date, with no airline or flight details. In our checks they matched the one-way and round-trip endpoints to the unit, but a full search for a date can return a different price, so confirm the date you pick with the one-way or round-trip endpoint before booking.
- Why is a price null?
- Google shows no fare for that date. Every date in the range gets a row; price is null where Google has none. A range with no priced date at all answers 200 with X-Search-Status: empty.
- Is the price per person?
- No: it is for all the adults you send, together. Children and infants are not taken on this endpoint.
- What happens when Google does not answer?
- A 503 with the standard failure body (search_status degraded, retry true). It is safe to send again.
A month of fares, one request
Google Flights' lowest fare for every date of a month, from your first call.
Free tier: 50 requests/month. No card to try.
Docs: the Flights API and the MCP servers.