Catalog

Google Flights API

Google Flights data through one normalized API - per-request USD pricing, no subscriptions, and automatic failover on redundant endpoints.

Endpoints1Providers2From · search$1.00/1k req · QuokkaFull breakdownRead docs
Uptime
100.00%
30d · 1 call
Requests
1
30d
Response
5.6s
median · 30d

Measured performance

What the Google Flights API actually does

Every call through AnyAPI over the last 30 days, counted here rather than promised.

100.0%
of calls succeeded (1 call)
Succeeded on first lane 100.0%
Response time (1 call)
Typical (p50)
5.6s
Half of requests finish within 5.6s
p99 response time
5.6s
p99 response time: 99% of requests finish within 5.6s

FAQ

About the Google Flights API

The AnyAPI Google Flights API returns Google Flights data as normalized JSON across 1 endpoint: search. You call one endpoint per job with a single key, and AnyAPI routes each request across 2 sources, falling back automatically when one fails. Pricing is in US dollars, from $1 per 1,000 requests, with no subscription and no monthly minimum. Over the last 30 days, 100.0% of Google Flights calls through AnyAPI succeeded, with a median response time of 5.6 seconds across 1 measured calls.

Pricing is in US dollars, from $1 per 1,000 requests, with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

One endpoint: search. Every one takes the same authentication and returns the same normalized response shape, so reaching a second Google Flights endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of Google Flights calls through AnyAPI succeeded, with a median response time of 5.6 seconds across 1 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.