science This product or feature is in Preview (pre-GA). Pre-GA products and features might have limited support, and changes to pre-GA products and features might not be compatible with other pre-GA versions. Pre-GA Offerings are covered by the
Google Maps Platform Service Specific Terms. For more information, see the
launch stage descriptions.
Geocoding API v4 overview
Stay organized with collections
Save and categorize content based on your preferences.
European Economic Area (EEA) developers
This release of Geocoding API v4 includes the release of the
following endpoints:
Geocoding API v4 is implemented on the service
infrastructure
on Google Cloud. This implementation brings with it a more secure and trusted
platform with enhanced security options like
OAuth. This standard API
design brings a level of consistency across the APIs that improve the efficiency
of development with Geocoding API v4.
OAuth support added
Geocoding API v4 supports the use of OAuth
2.0 for authentication. Google
supports common OAuth 2.0 scenarios such as those for a web server.
Field mask support added
Use field masks to specify what
information the response should return. For the Geocode an address,
Geocode a location, and
Place geocoding endpoints, all
fields in the response object are returned by default. For the
Search for destinations
endpoint, you must specify a field mask in the API request.
No cost for usage during Preview
Geocoding API v4 is in the pre-GA Preview stage, and there is no charge for
API usage during Preview. API calls will appear on the Billing page in the Cloud
Console, but charges will be $0.
Feedback
This is a Preview feature. We would appreciate feedback at
geocoding-feedback-channel@google.com.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-28 UTC.
[null,null,["Last updated 2025-08-28 UTC."],[],[],null,["# Geocoding API v4 overview\n\n**European Economic Area (EEA) developers** If your billing address is in the European Economic Area, effective on 8 July 2025, the [Google Maps Platform EEA Terms of Service](https://cloud.google.com/terms/maps-platform/eea) will apply to your use of the Services. Functionality varies by region. [Learn more](/maps/comms/eea/faq).\n\nThis release of Geocoding API v4 includes the release of the\nfollowing endpoints:\n\n- (Preview) [Geocode an address](/maps/documentation/geocoding/geocoding) --- Also called *forward geocoding*.\n- (Preview) [Geocode a location](/maps/documentation/geocoding/reverse-geocoding) --- Also called *reverse geocoding*.\n- (Preview) [Place geocoding](/maps/documentation/geocoding/places-geocoding) --- Retrieve an address from a place ID.\n- (Experimental) [Search for destinations](/maps/documentation/geocoding/search-for-destinations) --- Search for a destination from an address, place ID, or location.\n\nImplemented on the Google Cloud standard platform\n-------------------------------------------------\n\nGeocoding API v4 is implemented on the [service\ninfrastructure](https://cloud.google.com/service-infrastructure/docs/overview)\non Google Cloud. This implementation brings with it a more secure and trusted\nplatform with enhanced security options like\n[OAuth](/maps/documentation/places/web-service/oauth-token). This standard API\ndesign brings a level of consistency across the APIs that improve the efficiency\nof development with Geocoding API v4.\n\nOAuth support added\n-------------------\n\nGeocoding API v4 supports the use of [OAuth\n2.0](/maps/documentation/geocoding/oauth-token) for authentication. Google\nsupports common OAuth 2.0 scenarios such as those for a web server.\n\nField mask support added\n------------------------\n\nUse [field masks](/maps/documentation/geocoding/choose-fields) to specify what\ninformation the response should return. For the [Geocode an address](/maps/documentation/geocoding/geocoding),\n[Geocode a location](/maps/documentation/geocoding/reverse-geocoding), and\n[Place geocoding](/maps/documentation/geocoding/places-geocoding) endpoints, all\nfields in the response object are returned by default. For the\n[Search for destinations](/maps/documentation/geocoding/search-for-destinations)\nendpoint, you must specify a field mask in the API request.\n\nNo cost for usage during Preview\n--------------------------------\n\nGeocoding API v4 is in the pre-GA Preview stage, and there is no charge for\nAPI usage during Preview. API calls will appear on the Billing page in the Cloud\nConsole, but charges will be $0.\n\nFeedback\n--------\n\nThis is a Preview feature. We would appreciate feedback at\n[geocoding-feedback-channel@google.com](mailto:geocoding-feedback-channel@google.com)."]]
