Recipe · Flights API
One-way flight search with RapidAPI
The agent searches live Google Flights data and answers with fares it can actually judge: every result carries Google’s historical price band and a low | typical | high verdict, so “is the price any good” is a field read, not a guess. The buy_link hands the user a working booking deep link.
Free tier on RapidAPI. No card to try.
Step 1 · Connect
Call the listing host
The marketplace host is where the key comes from and where the usage meters. Same API, same request bodies; the only difference from our own domain is the host and the extra x-rapidapi-host header. Flights and hotels are separate listings with separate subscriptions.
curl -X POST "https://google-flights-live-api.p.rapidapi.com/api/google_flights/oneway/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":"LHR","to_airport":"JFK","departure_date":"2026-10-13"}'Bring your own RapidAPI key: every request is billed to your own subscription, never ours.
Step 2 · The job
The job
The job in plain words. In RapidAPI you express it as the configuration below instead of a prompt.
“Find me a nonstop JFK to Cancun flight on January 1 and tell me if the price is any good.”
Step 3 · Under the hood
The request
One POST, flat JSON in, flat JSON out. Field names are the ones in the OpenAPI spec.
POST https://google-flights-live-api.p.rapidapi.com/api/google_flights/oneway/v1
{
"from_airport": "JFK",
"to_airport": "CUN",
"departure_date": "2027-01-01",
"max_stops": 0,
"limit": 5
}Step 4 · Read the response
Fields your logic reads
The response is flat JSON. These are the fields this recipe branches on, with what each one means.
pricestringThe fare as Google Flights displays it: “$56”. The numeric twin price_as_number rides alongside for sorting and arithmetic.
price_insights_lownumber | nullThe bottom of Google’s historical price band for this route and dates. Null when Google doesn’t publish a band: treat the fare as unjudged, not bad.
price_insights_highnumber | nullThe top of the band. A fare above it is expensive for the route by Google’s own history.
price_range_in_relation_to_other_periods"low" | "typical" | "high" | nullGoogle’s verdict on the current fare against that band, the single field alerting, ranking, and “book now” logic branch on.
buy_linkstring (URL)A Google Flights deep link that reopens this exact itinerary. Hand it to the user; it just works.
Questions, answered plainly
- Is my key billed to me?
- Yes. The key is the one RapidAPI issued you, and usage meters against that subscription whichever host you call. There is no FlightPowers account and no second bill.
- Does this need a server of mine?
- No. It is one HTTPS request from whatever already runs your code. The OpenAPI spec is at flightpowers.com/openapi.json if you want to generate a client.
- What does it cost?
- The Google Flights Live API's free tier is 10 requests/month with a hard cap: enough to verify your key works, not to evaluate. The PRO plan is $10/month for 2,500 requests, and every plan includes every endpoint.
Also works with
One-way flight search, elsewhere in your stack
More recipes
More to build in RapidAPI
Get live flight and hotel data
Live Google Flights and Booking.com data as clean JSON. Free tier on RapidAPI, no card to try.
Free tier: 10 requests/month. No card to try.