Recipe · Flights API
Price-insights check with Apify
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.
Pay-per-event on your own Apify account. No monthly plan.
Step 1 · Connect
Run the actor
Pay-per-event through your own Apify account: no monthly plan, and an idle month costs nothing. The input field names and the endpoint values are the actors’ own published input schemas, read from api.apify.com on 2026-09-02. Nothing to subscribe to on RapidAPI for this path.
curl -X POST "https://api.apify.com/v2/acts/mtnrabi~google-flights-real-time-api/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"endpoint":"oneway","from_airport":"LHR","to_airport":"JFK","departure_date":"2026-10-13","currency":"usd"}'Billed per event on your own Apify account. No RapidAPI subscription needed for this path.
Step 2 · The job
The job
The job in plain words. In Apify 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
The actor input
Paste this into the actor’s Input tab, or send it as the JSON body of a run. Field names come from the actor’s own published input schema.
// actor: mtnrabi~google-flights-real-time-api
{
"endpoint": "oneway",
"from_airport": "JFK",
"to_airport": "CUN",
"departure_date": "2027-01-01",
"currency": "usd",
"limit": 3
}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?
- Not to RapidAPI. This path bills pay-per-event through your own Apify account, so an idle month costs nothing. The RapidAPI subscription and the Apify actor are two separate doors to the same data; you need one, not both.
- Does this need a server of mine?
- No. The actor runs on Apify’s infrastructure, and runs, retries and result storage live in your Apify console alongside your other actors.
- What does it cost?
- On this path, whatever the actor’s own event table charges for the events a run fires. There is no monthly plan and no minimum. The current rates are on the actor listing, which is the only place they are authoritative. If you would rather have a fixed monthly bill and synchronous HTTP, the RapidAPI plans are the other door: see /pricing.
Also works with
Price-insights check, elsewhere in your stack
More recipes
More to build in Apify
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.