Skip to content
throttle
Menu
HomeAPI LimitsGoogle Maps

Maps and Location

Google Maps Platform APIs

APIs and SDKs for maps, geocoding, places, routes, and location-based applications.

PUBLISHED PROVIDER LIMITS

Limits keep their provider-specific dimensions.

Quota values and enforcement dimensions vary by Maps Platform API and can be managed in Google Cloud Console.

Authentication: API key, OAuth 2.0 where supported

Primary scope: Google Cloud Project And Individual Maps Platform API

Measured dimensions: Queries, Requests, Billable Usage

Profile coverage: Published geocoding query limits and the project and API-specific quota model. Individual Maps Platform API quotas, billable usage caps, and product-specific response formats remain outside this profile.

API Quota

Google Maps Platform APIs API Quota
LimitValuePeriodScopeConditions and variability
Geocoding service3,000 queriesPer minuteProjectCombined client-side and server-side geocoding queries
Geocoding API v4 preview limit25 queriesPer secondProjectDuring the Geocoding API v4 preview Quota configuration and approved increases can change the effective project allowance.
Other Maps Platform API quotasProvider-specificProvider-definedProject And APIValues and dimensions vary by API and are normally reviewed and managed in Google Cloud Console.

RESPONSE METADATA

No shared rate-limit headers are published.

No general rate-limit response headers are documented in the sources reviewed for this profile. Use product-specific response data and quota controls.

WHEN A LIMIT IS EXCEEDED

Read the response before choosing a delay.

  • Rate-limit responses can use HTTP 429.
  • Maps APIs can also report product-specific quota states in response bodies or SDK status values.

RECOMMENDED HANDLING

Protect both the provider and your own queue.

  • Apply exponential backoff with jitter to transient quota responses.
  • Review the quota for the specific Maps Platform API in Google Cloud Console.
  • Keep billable usage controls separate from request-rate capacity planning.

VERIFICATION RECORD

Official sources reviewed