Google Places · Rate Limits

Google Places Rate Limits

Google Places API (New) enforces rate limits per API method per Google Cloud project. Each method (Text Search, Nearby Search, Place Details, Place Photos, Autocomplete) has its own independent per-minute quota. The default per-minute quota is configurable in the Google Cloud Console under Google Maps Platform > Quotas, and can be raised by request. Limits are scoped to the project rather than to an individual API key or IP. Quota-exceeded and throttled requests return HTTP 429 with the gRPC status RESOURCE_EXHAUSTED. The numeric default is not published as a fixed value on the docs page and must be confirmed per project in the Cloud Console.

Google Places Rate Limits is the machine-readable rate-limit profile for Google Places on the APIs.io network, in the API Commons Rate Limits shape.

It captures 2 rate-limit definitions, measuring requests_per_minute and requests_per_day.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and quotaExceeded.

Tagged areas include Geolocation, Google, Maps, Places, and Rate Limiting.

2 Limits Exhausted: HTTP 429 Quota: 429
Method: generated, dated 2026-06-02.
Written by API Evangelist on 2026-06-02 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
GeolocationGoogleMapsPlacesRate Limiting

Limits

Per-method per-minute quota project/method
requests_per_minute
per-method, configurable in Cloud Console > Google Maps Platform > Quotas
Each Places API method has a separate per-minute quota counted against the project. Adjustable and raisable via a quota increase request.
Daily quota cap (optional) project
requests_per_day
optional cap set by the project owner to control spend
Project owners may set a daily request cap per API to limit billing exposure; not enforced by default.

Policies

Per-Method Scoping
Rate limits are applied independently to each API method, so heavy use of Text Search does not consume the quota available to Place Details.
Backoff Strategy
On HTTP 429 (RESOURCE_EXHAUSTED), clients should retry with exponential backoff and jitter rather than immediate retry.
Quota Management
View and adjust per-method per-minute quotas in the Google Cloud Console under Google Maps Platform > Quotas; request increases through the console when sustained higher throughput is required.
Spend Capping
Set daily request caps and budget alerts to bound cost, since billing is usage-based per SKU rather than a fixed plan quota.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/google-places-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.