Field masking is required. You must specify which fields you want returned
in the response. There is no default list of returned fields. If you omit
this list, the methods return an error. For more information, see
FieldMask.
Place Details (New) supports both
API keys
and OAuth
tokens as the authentication mechanism.
Only JSON is supported as a response format in Place Details (New).
The JSON response format for Places API (New)
has changed from the format of the legacy APIs. For more details, see
Migrate the Places API response.
The following table lists parameters in Place Details (Legacy) that have been
renamed or modified for Place Details (New), or parameters that are no
longer supported.
Current parameter
New parameter
Notes
place_id
places/PLACE_ID
The string places/PLACE_ID is also called the
place resource name. In the response from a Place Details (New),
Nearby Search (New), and Text Search (New)
request, this string is contained in the name field of the response.
The standalone place ID is contained in the id field of the response.
language
languageCode
region
regionCode
Example request
The following example GET request uses the Place Details (Legacy). In this
example, you request a JSON response containing information about a place ID and
pass all parameters as URL parameters. This example also uses fields so the
response only includes the display name and formatted address of the place:
curl -L -X GET \
'https://maps.googleapis.com/maps/api/place/details/json?place_id=ChIJj61dQgK6j4AR4GeTYWZsKWw&fields=name%2Cformatted_address&key=API_KEY'
With Place Details (New), you make a GET request and pass all parameters
in URL parameters and headers as part of the request. This example also uses a
field mask so the response only includes the display name and formatted address
of the place:
The string places/PLACE_ID is also called the place
resource name. In the response from a Place Details (New),
Nearby Search (New), and Text Search (New) request, this string
is contained in the name field of the response. The standalone place ID is
contained in the id field of the response.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-21 UTC."],[],[],null,["**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\nIntroduction\n\nPlaces API supports\n[Place Details (Legacy)](/maps/documentation/places/web-service/details).\nIf you are familiar with Places API (Legacy), [Place Details (New)](/maps/documentation/places/web-service/place-details)\nmakes the following changes:\n\n- Field masking is required. You must specify which fields you want returned in the response. There is no default list of returned fields. If you omit this list, the methods return an error. For more information, see [FieldMask](/maps/documentation/places/web-service/place-details#fieldmask).\n- Place Details (New) supports both [API keys](/maps/documentation/places/web-service/get-api-key) and [OAuth](/maps/documentation/places/web-service/oauth-token) tokens as the authentication mechanism.\n- Only JSON is supported as a response format in Place Details (New).\n- The JSON response format for Places API (New) has changed from the format of the legacy APIs. For more details, see [Migrate the Places API response](/maps/documentation/places/web-service/migrate-response).\n\nThe following table lists parameters in Place Details (Legacy) that have been\nrenamed or modified for Place Details (New), or parameters that are no\nlonger supported.\n\n| Current parameter | New parameter | Notes |\n|-------------------|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `place_id` | `places/`\u003cvar translate=\"no\"\u003ePLACE_ID\u003c/var\u003e | The string `places/`\u003cvar translate=\"no\"\u003ePLACE_ID\u003c/var\u003e is also called the place *resource name* . In the response from a Place Details (New), Nearby Search (New), and Text Search (New) request, this string is contained in the `name` field of the response. The standalone place ID is contained in the `id` field of the response. |\n| `language` | `languageCode` | |\n| `region` | `regionCode` | |\n\nExample request\n\nThe following example GET request uses the Place Details (Legacy). In this\nexample, you request a JSON response containing information about a place ID and\npass all parameters as URL parameters. This example also uses `fields` so the\nresponse only includes the display name and formatted address of the place: \n\n```curl\ncurl -L -X GET \\\n'https://maps.googleapis.com/maps/api/place/details/json?place_id=ChIJj61dQgK6j4AR4GeTYWZsKWw&fields=name%2Cformatted_address&key=API_KEY'\n```\n\nWith Place Details (New), you make a GET request and pass all parameters\nin URL parameters and headers as part of the request. This example also uses a\nfield mask so the response only includes the display name and formatted address\nof the place: \n\n```\ncurl -X GET -H 'Content-Type: application/json' \\\n-H \"X-Goog-Api-Key: API_KEY\" \\\n-H \"X-Goog-FieldMask: displayName,formattedAddress\" \\\nhttps://places.googleapis.com/v1/places/ChIJj61dQgK6j4AR4GeTYWZsKWw\n```\n\nThe string `places/`\u003cvar translate=\"no\"\u003ePLACE_ID\u003c/var\u003e is also called the place\n*resource name* . In the response from a Place Details (New),\nNearby Search (New), and Text Search (New) request, this string\nis contained in the `name` field of the response. The standalone place ID is\ncontained in the `id` field of the response.\n| **Note:** In the [Place Details (Legacy)](/maps/documentation/places/web-service/details), the `name` field of the response contained the human-readable name for the place. In the new API, that field is now called `displayName`."]]