Recipe · Flights API
Price-insights check with Make
The recipe that only this API can run: the agent compares a quoted fare against Google’s own price band for the route and dates. Below the band’s low end → take it; above the high end → wait. The verdict field gives the agent a defensible recommendation with a source.
Free tier on RapidAPI. No card to try.
Step 1 · Connect
HTTP → Make a request
Set Parse response to Yes and the JSON fields become mappable in every later module. No dedicated Make app is needed; the generic HTTP module is the whole integration.
URL https://api.flightpowers.com/v1/flights/oneway
Method POST
Body type Raw
Content type JSON (application/json)
Headers x-api-key: YOUR_RAPIDAPI_KEY
Parse response YesBring 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 Make you express it as the configuration below instead of a prompt.
“I was quoted $129 for JFK→Cancún on January 1. Should I take it?”
Step 3 · Under the hood
What goes in the request body
Paste this as the raw JSON body. Field names are the ones in the OpenAPI spec, so nothing here needs translating.
POST https://api.flightpowers.com/v1/flights/oneway
{
"from_airport": "JFK",
"to_airport": "CUN",
"departure_date": "2027-01-01",
"limit": 3
}The band and the verdict ride on every result of the ordinary search. There is no separate insights endpoint to call and nothing extra to enable.
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.
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.
Questions, answered plainly
- Is my key billed to me?
- Yes. The key you put in the Make step is your own RapidAPI key, and every run meters against your own subscription. Make bills you separately for its own runs; the two bills never mix.
- Does this need a server of mine?
- No. Make calls api.flightpowers.com over plain HTTPS. There is nothing to host, and no callback for us to reach.
- 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
Price-insights check, elsewhere in your stack
More recipes
More to build in Make
One-way flight search
Flights API · search_oneway_flights
Round-trip search
Flights API · search_roundtrip_flights
Cheapest-date scan
Flights API · search_oneway_flights
Hotel search
Hotels API · search_hotels
Rate-parity check
Hotels API · find_hotel_by_name
Fare-alert cron
Flights API · search_oneway_flights
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.