Recipe · Flights API
Round-trip search with Zapier
Round-trip is a first-class paired-leg search: one object per itinerary with both legs already matched and a combined total, not two one-way lists the agent has to cross-join. The agent reads total_price and presents real bookable combinations.
Free tier on RapidAPI. No card to try.
Step 1 · Connect
Webhooks by Zapier → Custom Request
A native Zapier app is in review and not listed yet, so this page documents the built-in Webhooks step, which works today. Zapier parses the JSON response, so every field below is mappable in later steps.
URL https://api.flightpowers.com/v1/flights/oneway
Method POST
Headers x-api-key: YOUR_RAPIDAPI_KEY
Content-Type: application/jsonBring 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 Zapier you express it as the configuration below instead of a prompt.
“I need a round trip New York to Paris, out October 6, back October 13. What are my options?”
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/roundtrip
{
"from_airport": "JFK",
"to_airport": "CDG",
"departure_date": "2026-10-06",
"return_date": "2026-10-13",
"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.
total_pricestringThe combined price of the paired round-trip itinerary: one number for both legs, because they were searched together. total_price_as_number is the integer.
total_duration_secondsnumberTravel time across both legs, in seconds, sortable without parsing a display string.
departure_flight_airlinestringOperating carrier on the outbound leg.
return_flight_airlinestringOperating carrier on the return leg, paired to the same itinerary, not cross-joined.
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 you put in the Zapier step is your own RapidAPI key, and every run meters against your own subscription. Zapier bills you separately for its own runs; the two bills never mix.
- Does this need a server of mine?
- No. Zapier 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
Round-trip search, elsewhere in your stack
More recipes
More to build in Zapier
One-way flight search
Flights API · search_oneway_flights
Price-insights check
Flights API · search_oneway_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.