Google Flights data: pay per itinerary or per search?
Last updated
Maintained by Datapika · We publish this product under the openclawai account on Apify. Product reference
Datapika charges a named event per returned itinerary; SerpApi sells search allowances. Those are different billing units. Choose based on your query volume, itinerary yield, required follow-up requests, and integration needs. This comparison documents public prices and interfaces, not measured speed or fare accuracy.
Scroll the table sideways to inspect every column →
| Provider / product | Listed base price | What the headline excludes | Store evidence / source |
|---|---|---|---|
| Our productDatapika Google Flights Result-based itinerary exports through the Apify API. | $1.50/ 1,000 itineraries | Start, dataset and platform usage charges may be additional. No store reviews at the snapshot date. | 12 total users No store reviews yet Inspect source |
| SerpApi Google Flights A search API with documented multi-city and follow-up flight requests. | $25.00/ month · 1,000 searches | Starter subscription. A search is billed independently of how many results it returns. Free allowance: 250 searches/month. | Not an Apify actor; store statistics do not apply. Inspect source |
Do not divide a search subscription into an itinerary price without measuring actual yield. These products retrieve search data; they do not issue tickets.
Why $1.50 and $25 are not an apples-to-apples comparison
Datapika lists $0.0015 per itinerary event, so 1,000 itinerary events total $1.50 before additional dataset, actor-start, and platform usage charges. That calculation says nothing about how many searches are needed to obtain those itineraries.
SerpApi’s Starter plan is $25 per month for 1,000 searches at the review date. Its pricing page says a search is counted independently of the number of returned results, and it also lists a free allowance. Do not present a search subscription as an itinerary price or infer a savings percentage without measuring yield.
- Keep searches and returned itineraries in separate columns.
- Include follow-up requests when designing a round-trip workflow.
- Prices are a September 4 snapshot; verify the vendor before purchase.
What should a flight-data sample contain?
Hold the route, date, passenger count, cabin, currency, and trip type constant when evaluating providers. Check whether output represents an individual segment or a complete itinerary, and compare elapsed duration and stop count as well as the displayed price.
Datapika’s input schema supports airport codes, dates, trip and seat settings, and a maximum itinerary count. SerpApi documents multi-city inputs and follow-up flight requests. Those documented capabilities are not proof that every route or fare will be available.
- Verify route and date interpretation before comparing fares.
- Retain a collection timestamp; travel prices change.
- These data products do not issue a ticket or guarantee booking availability.
Which model fits your workflow?
Consider Datapika for itinerary exports using the Apify platform. Consider SerpApi if a search-based API and its documented query and follow-up options fit your integration. Neither recommendation establishes a winner on price or accuracy.
Datapika’s Google Flights actor had no store reviews at the snapshot date. That limitation belongs in the comparison just as much as the event price. Evaluate a small representative sample before using either service for a customer-facing price experience.
- Measure useful itineraries per search for your own routes.
- Compare full invoices only after the output scope is aligned.
- Do not infer uptime from an actor’s total run count.
Sources you can inspect
Comparison sources reviewed September 4, 2026. These references describe supported options and billing, not independent proof of performance. Confirm current details before running; examples and estimates are not guarantees.
How to do it
- 1.Define the output fields and exact query scope your workflow needs.
- 2.Open each linked source and verify the current billing unit, extras, and any scheduled changes.
- 3.Run your own bounded sample with matching inputs; record missing fields, duplicates, and total charges.
- 4.Choose the provider on usable output and full cost. Repeat the check when requirements or pricing change.
Questions, answered
Can I use this data to book a flight?
These products retrieve flight search information. They are not ticket-issuing or booking services, and a collected price does not guarantee a fare remains bookable.
Which Google Flights API is cheapest?
This snapshot cannot establish an all-in cheapest provider. The products bill different units, and the total depends on search volume, result yield, follow-up requests, subscriptions, and additional usage charges.