Enrich a Postal Address into a Full Place Record
A 2-step recipe with Google Maps Platform. We can help you get access.
Recipe · 2 steps
Enrich a Postal Address into a Full Place Record
with Google Maps Platform
Turn a stored postal address into a canonical, enriched Google place record.
- Forward geocode the address to obtain its place ID plus the precision signals. Read location_type and partial_match from the outputs before trusting anything downstream of this step.
- Read the Places record behind the geocoded place ID. Place IDs are shared across Google Maps Platform, so the identifier the Geocoding API minted is directly addressable here without any re-searching by name.
What you'll need to have ready
- address: The postal address to resolve (e.g. "1600 Amphitheatre Parkway, Mountain View, CA").
- apiKey: Google Maps Platform API key. The Geocoding API takes the key as the required `key` query parameter; the Places API takes it as the X-Goog-Api-Key header applie
- components: Pipe-separated component filter constraining the geocode to a country, postal code, or locality (e.g. "country:US|postal_code:94043"). Setting this is the cheap
- region: ccTLD two-character region code used to bias geocoding (e.g. "us").
- language: Language in which to return the geocoding results (e.g. "en").
- detailsFieldMask: Comma-separated Place Details fields to return. Field masking is the primary cost lever on the Places API - request only what you store.
- languageCode: BCP-47 language code for the Places response (e.g. "en").
- regionCode: CLDR region code used to bias the Places response (e.g. "US").
For your developer
Arazzo workflow google-maps:address-to-place-details, 2 operations: geocode → getPlaceDetails. Specs on APIs.io.