01 / overview

A wrong address is expensive. The Geocoding API is how Google fixes it before it ships.

Every misrouted delivery, failed geofence, and location field that won't join to another system traces back to the same root cause: an address that was never resolved to a real point on the map. The Geocoding API is the same geocoder behind the Google Maps search box — turn a street address into a precise latitude/longitude, or run it in reverse to turn a GPS fix into a human-readable address, continuously kept in sync with the real world.

See what's included Coverage & pricing

in one line

It is: an address↔coordinate conversion API, plus (in v4) destination lookups built for routing and delivery.
It is not: an address-validation or deliverability-certification product — it resolves a location, it doesn't confirm a mailing address is correct or deliverable.

Geocoding API overview docs

geocode() resultv4 · GA

formattedAddressSTRING

locationLatLng

granularityENUM

placeIdSTRING

addressComponentsARRAY

···· viewport, plusCode, types

0countries & territories covered

0monthly Google Maps users on the same map data

0free geocodes every month

0USD / 1,000 requests to start

02 / what's included

One schema, whether it's one address or ten million

Forward geocoding turns an address (or a place ID) into a location. Reverse geocoding turns a location (or a place ID) back into a structured, human-readable address. Both return the same shape every time — a formatted address, structured address components, a place ID, and a precision signal telling you exactly how much to trust the result, so downstream code never has to guess.

Included

Forward geocoding (address → lat/lng)
Reverse geocoding (lat/lng → address)
Place ID lookup either direction
Component filtering (country, postal code)
4 precision tiers: ROOFTOP, RANGE_INTERPOLATED, GEOMETRIC_CENTER, APPROXIMATE

Not included

Deliverability validation (Address Validation API)
Autocomplete-as-you-type (Places API)
Turn-by-turn routing (Routes API)
Place attributes at scale (Places Insights)

Forward geocoding request/response Reverse geocoding request/response

precision levels (location_type)

ROOFTOPRANGE_INTERPOLATED GEOMETRIC_CENTERAPPROXIMATE

request parameters

addresslatlng placeIdcomponents boundsregion language

03 / why google's data

Accuracy isn't a snapshot here — it's a live feed

A geocoder is only as good as the map underneath it, and most competing address-lookup tools are working from a licensed extract that goes stale the moment it's shipped. This one is built on Google's own map data — the same map that over 2 billion people use every month to find real places, which means someone besides you is already reporting when a road changes or a new building goes up.

key facts

coverage across 250+ countries and territories
the underlying map data is continuously updated, not licensed as a static extract
the identical dataset and infrastructure behind the Google Maps app itself — there's no separate, lower-fidelity "API tier" of the map

Coverage details

Real-world signalsroads, buildings, businesses change

Google Maps' living mapcontinuously reconciled, not a static extract

Geocoding APIyour address, resolved against a current map

04 / v3 → v4

v4 is GA — and it adds a destination-aware method

The classic Geocoding API (v3) still works and still returns snake_case JSON with an API key. Version 4 is generally available on Google Cloud's newer service infrastructure: camelCase fields, optional OAuth, and a third method beyond geocode/reverseGeocode — searchDestinations, purpose-built for routing and pickup/delivery, returning building outlines, entrances, navigation points, and AI-generated summaries.

v4 specifics

three channels: /v4/ (GA), /v4beta/ (preview), /v4alpha/ (experimental)
default quota 25 queries/sec; designed to be called server-to-server, not from the client
v3's experimental BUILDING_AND_ENTRANCES parameter is retired — that data now comes from searchDestinations

Geocoding API v4 overview v3 to v4 migration guide

geocode()address → location

reverseGeocode()location → address

searchDestinations()v4-only · outlines, entrances, nav points

05 / address descriptors

When a formal address isn't enough

Address Descriptors add landmark- and area-based context to a geocoding result — useful anywhere addressing is informal or a rooftop point alone doesn't tell a driver where to actually go. A result can say a point is WITHIN, BESIDE, ACROSS_THE_ROAD from, or DOWN_THE_ROAD from a nearby landmark, and which named neighborhood or complex it's NEAR, WITHIN, or on the OUTSKIRTS of.

availability

generally available across India since April 2025, at no extra cost on top of the Geocoding (India) Essentials SKU
Experimental launch stage everywhere else

Address Descriptors request/response Coverage expansion announcement

landmark relationships

WITHINBESIDE ACROSS_THE_ROADDOWN_THE_ROAD

area containment

NEARWITHINOUTSKIRTS

06 / extend with maps platform

The address resolver the rest of Maps Platform builds on

Geocoding is usually step one, not the whole workflow. Once you have a place ID or a precise location, bridge straight into the API built for the next step — no separate vendor, no separate address model to reconcile.

Every one of these runs on the same Google Cloud billing account and the same API key management as the Geocoding API itself — one platform relationship to negotiate and support, not four.

Address Validation APIConfirm an address is real and deliverable before you commit to shipping or billing against it.

Places API & Place DetailsPull live hours, photos, and reviews for the place ID a geocode result already gave you.

Routes APIFeed geocoded origins and destinations straight into routing and ETA calculations.

Places InsightsJoin a geocoded location against 300M+ places in BigQuery for category, rating, and brand context.

Address Validation API docs Routes API docs

pairs well with

Address Validation API Places API Routes API Places Insights Maps JavaScript API BigQuery

07 / example requests

What a request actually looks like

One forward, one reverse — the classic v3 REST shape. Click run on either card; these are mocked responses, not a live connection.

forward geocoding

an address to a rooftop-precision location

GET https://maps.googleapis.com/maps/api/geocode/json
    ?address=1600+Amphitheatre+Parkway,+Mountain+View,+CA
    &key=YOUR_API_KEY

200 OK · 0.3s elapsed

field	value
formatted_address	1600 Amphitheatre Parkway, Mountain View, CA 94043, USA
location	37.4224764, -122.0842499
location_type	ROOFTOP
place_id	ChIJ2eUgeAK6j4ARbn5u_wAGqWA

reverse geocoding

a lat/lng to a structured street address

GET https://maps.googleapis.com/maps/api/geocode/json
    ?latlng=40.714224,-73.961452
    &result_type=street_address
    &key=YOUR_API_KEY

200 OK · 0.3s elapsed

field	value
formatted_address	277 Bedford Ave, Brooklyn, NY 11211, USA
types	street_address
place_id	ChIJd8BlQ2BZwokRAFUEcm_qrcA

Get started with Geocoding API v4

08 / use cases and industries

Where the Geocoding API gets used

Almost every workflow that puts a location on a map, calculates a route, or joins data by place starts by resolving an address or a coordinate first.

Delivery & logisticsResolve drop-off addresses to precise, routable coordinates, and use searchDestinations for the correct building entrance.

Store locators & site mappingTurn a spreadsheet of store or branch addresses into map-ready points in bulk.

Data enrichmentStandardize inconsistent address text in CRM or customer data into clean coordinates and address components for joins.

Risk & underwritingPlace a policyholder's address precisely enough to layer on flood zones, crime, or other spatial risk data.

Ride-hailing & mobilityResolve pickup requests, including landmark-based ones, to an exact meeting point.

Emergency & field dispatchConvert a caller's coordinates into a readable address, or an address into a location a crew can navigate to.

industries

Logistics & delivery Retail & QSR Real estate Insurance Ride-hailing & mobility Telecom Government & public safety Field services

09 / reliability

Backed by an SLA, not a best-effort promise

If you're putting this in front of an address-resolution step that a delivery, a dispatch, or a checkout flow depends on, uptime isn't a nice-to-have — it's the actual pitch. The Geocoding API carries Google Cloud's standard Maps Platform commitment, with public, auditable status history.

the commitment

99.9% monthly uptime SLA
service credits owed if Google misses it

the proof

public status dashboard, 365 days of incident history
the same infrastructure serving Google Maps' 2B+ monthly users

Maps Platform SLA terms Public status dashboard

Your request 99.9% SLAcredits if missed Resolved location

Any incident Public dashboard365-day history You can verify it yourself

10 / coverage and pricing

Global coverage, and the math works in your favor at scale

Coverage follows Google Maps itself — there's no separate per-country dataset to buy. Pricing is volume-tiered per 1,000 requests and it steps down as you grow, with the first 10,000 calls every month free.

free tier & bundling

10,000 geocoding calls free every month
also bundled into the Starter plan ($100/mo, 50,000 calls) alongside other Maps Platform APIs

Do the arithmetic on the table on the right: geocoding a million-record customer file lands around $1,500 at the 1M–5M tier — a rounding error next to what one misrouted shipment or one failed field-service dispatch actually costs.

Maps Platform pricing reference

monthly volume	price / 1,000
0 – 10,000	Free
10,001 – 100,000	$5.00
100,001 – 500,000	$4.00
500,001 – 1,000,000	$3.00
1,000,001 – 5,000,000	$1.50
5,000,000+	$0.38

Rates shown are Google's list pricing for the core Geocoding API as of this writing and are billed against your Google Cloud billing account; confirm current rates before quoting. Address Validation API, a separate product, is priced and tiered differently.

11 / get started

Nothing here needs a commitment to try

The free 10,000-call tier is enough to run a real proof of concept against your own address data before anyone signs anything — and everything you build against v4 today scales straight into production on the same key.

Read the v4 quickstart Review pricing again

Google Maps Platform: get started hub

1

Enable the API and generate a keya few clicks in Google Cloud Console; restrict the key to the Geocoding API before it leaves your desk

2

Run it against real addressesthe free 10,000/month tier is enough for a genuine proof of concept, not a toy demo

3

Scale with confidencevolume pricing steps down automatically and the 99.9% SLA applies the same on day one and at scale