Catalog
Google Hotels

Google Hotels API

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

Endpoints2Providers2From · search$1.50/1k req · QuokkaFull breakdownRead docs
Uptime
100.00%
30d · 9 calls
Requests
9
30d
Response
7.8s
median · 30d

Measured performance

What the Google Hotels API actually does

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

100.0%
of calls succeeded (9 calls)
Succeeded on first lane 66.7%Recovered by failover 33.3%
Response time estimate (9 calls across endpoints)
Weighted p50 estimate
7.8s
Request-weighted average of endpoint p50 values, not a combined request percentile
Weighted p99 estimate
15.0s
Request-weighted average of endpoint p99 values, not a combined request percentile

FAQ

About the Google Hotels API

The AnyAPI Google Hotels API returns Google Hotels data as normalized JSON across 2 endpoints: details and 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.50 per 1,000 requests on the cheapest endpoint, with no subscription and no monthly minimum. Over the last 30 days, 100.0% of Google Hotels calls through AnyAPI succeeded, with a request-weighted median response time of 7.8 seconds across 9 measured calls.

Pricing is in US dollars, from $1.50 per 1,000 requests on the cheapest endpoint, 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.

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

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