**European Economic Area (EEA) developers** > [!NOTE] > 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](https://developers.google.com/maps/comms/eea/faq.md.txt). This document describes the steps you need to start using the Places API (New). ## Prerequisites This procedure guides you through setting up a Google Cloud Account and Google Cloud project with billing enabled. You should also be familiar with how you are charged for using the Places API (New). 1. **Review** billing and cost for usage at [Places API (New) Usage and Billing](https://developers.google.com/maps/documentation/places/web-service/usage-and-billing.md.txt). 2. **Verify** that you have a [Google Cloud Account](https://support.google.com/accounts/answer/15277265). [Sign in to the Google Cloud console](https://console.cloud.google.com/google/maps-apis/overview?utm_source=Docs_SignIn&utm_content=Docs_places&ref=/maps/documentation/places-web-service/get-api-key) > [!NOTE] > **Note:** If you are a new user and don't have a Google Cloud Account, meaning you cannot sign in to the console, see [Getting started with Google Maps Platform](https://developers.google.com/maps/get-started.md.txt). 3. **Verify** that you have a [Google Cloud project](https://cloud.google.com/apis/docs/getting-started#creating_a_google_project) with billing enabled. [Go to the Billing page](https://console.cloud.google.com/projectselector/billing?utm_source=Docs_Billing&utm_content=Docs_places&ref=/maps/documentation/places-web-service/get-api-key) > [!NOTE] > **Note:** If you are a new user and don't have a Google Cloud project, see [Getting started with Google Maps Platform](https://developers.google.com/maps/get-started.md.txt). 1. Select your project to open the **Billing** page. 2. On the **Billing** page: - If billing is already enabled for the selected project, and you only have a single billing account, then the **Billing** page opens. - If you have multiple billing accounts, select **Go to linked billing account** to see the details about the billing account associated with the project. - If a billing account exists but is not associated with the project, you are prompted to link a billing account with the project. - If no billing account exists, or you want to create a new billing a account, select **Manage Billing Accounts** to create a new billing account. For more information, see [Create a new self-serve Cloud Billing account](https://cloud.google.com/billing/docs/how-to/create-billing-account). ## Enable the API Before you can use Places API (New), you must use the Google Cloud console or the [`gcloud`](https://cloud.google.com/sdk) command to enable it in your Google Cloud project. > [!NOTE] > **Note:**After you enable an API you might have to wait a few minutes before you can make a request to it. To enable the API: ### Console 1. Open the product page in the Google Cloud console: [Enable the Places API (New)](https://console.cloud.google.com/apis/library/places.googleapis.com?utm_source=Docs_EnableAPIs&utm_content=Docs_places&ref=/maps/documentation/places-web-service/get-api-key) 2. Click the **Enable** button. > [!NOTE] > **Note:** If the API is already enabled, you see the **Manage** button instead of **Enable**. ### gcloud ```bash gcloud services enable \ --project "PROJECT" \ "places.googleapis.com" ``` Read more about the [Google Cloud SDK](https://cloud.google.com/sdk), [Cloud SDK installation](https://cloud.google.com/sdk/docs/install), and the following commands: - [`gcloud services enable`](https://cloud.google.com/sdk/gcloud/reference/services/enable) - [`gcloud services disable`](https://cloud.google.com/sdk/gcloud/reference/services/disable) ## Get an API key for use with Places API (New) > [!IMPORTANT] > **Key Point:** This setup guide includes the procedure for both **configuring an API key** and **creating an OAuth token**. Choose the procedure that is applicable for your deployment environment. Google Maps Platform products are secured from unauthorized use by requiring API calls to include **either** an **API key** or **OAuth token** . The API key procedure comes first. To use an OAuth token instead, see [Create an OAuth token](https://developers.google.com/maps/documentation/places/web-service/get-api-key.md.txt#create-an-oauth-token). An [API key](https://cloud.google.com/docs/authentication/api-keys) is a unique alphanumeric string that associates your Cloud Billing account and Google Cloud project with the request your application makes to a Google Maps Platform API or SDK. To create a new key or add an API or SDK to an existing key, follow these instructions. ### Console 1. Go to the **Google Maps Platform \> Keys \& Credentials** page. [Go to the Keys \& Credentials page](https://console.cloud.google.com/projectselector/google/maps-apis/credentials?utm_source=Docs_ManageAPIKey&utm_content=Docs_places&ref=/maps/documentation/places-web-service/get-api-key) 2. If prompted, select your project. 3. Do one of the following: - **Create a new key**: 1. Click **Create credentials \> API key**. 2. In the **Create API key** panel, open the **Select API restrictions** list. 3. Clear any APIs that this key doesn't need, and make sure **Places API (New)** stays selected. 4. Click **Create**. The panel displays your new API key. - **Use an existing key**: 1. Click the name of the key. 2. In the **Select API restrictions** list, select **Places API (New)**. 3. Click **Save**. Selecting an API here doesn't enable it. Make sure Places API (New) is enabled on its [API Library page](https://console.cloud.google.com/apis/library/places.googleapis.com). 4. To see the key string later, go to the **Keys \& Credentials** page and click **Show key** for the key. If the console looks different from these steps, see [Create an API key](https://cloud.google.com/docs/authentication/api-keys#create) and [Add API restrictions](https://cloud.google.com/docs/authentication/api-keys#adding-api-restrictions) in the Google Cloud documentation. ### gcloud Replace PROJECT_ID with your project ID in the following commands. - **Create a new key** : Run the following command, and replace DISPLAY_NAME with a name for the key. ```bash gcloud services api-keys create \ --project="PROJECT_ID" \ --display-name="DISPLAY_NAME" \ --api-target=service=places.googleapis.com ``` Read more about the [Google Cloud SDK](https://cloud.google.com/sdk), [Cloud SDK installation](https://cloud.google.com/sdk/docs/install), and the following commands: - [`gcloud services api-keys create`](https://cloud.google.com/sdk/gcloud/reference/services/api-keys/create) - **Use an existing key** : Run the following command, and replace KEY_ID with the ID of the key. The `--append` flag keeps the APIs that the key already allows. Without it, the command replaces them. ```bash gcloud services api-keys update KEY_ID \ --project="PROJECT_ID" \ --append \ --api-target=service=places.googleapis.com ``` Read more about the [Google Cloud SDK](https://cloud.google.com/sdk), [Cloud SDK installation](https://cloud.google.com/sdk/docs/install), and the following commands: - [`gcloud services api-keys update`](https://cloud.google.com/sdk/gcloud/reference/services/api-keys/update) - [`gcloud services api-keys list`](https://cloud.google.com/sdk/gcloud/reference/services/api-keys/list) The key ID isn't the key string or display name. To find it, run `gcloud services api-keys list --project="PROJECT_ID"`. The ID is the last part of the `name` field: `projects/PROJECT_NUMBER/locations/global/keys/KEY_ID`. To see the key string, run `gcloud services api-keys get-key-string KEY_ID --project="PROJECT_ID"`. ## Make an API request Make a Places API (New) request to return a JSON response for a Text Search on the string "Spicy Vegetarian Food in Sydney, Australia". You must include your API key's alphanumeric string with every request and use HTTPS for requests that include the API key. 1. Click API_KEY in the code below to insert the key's alphanumeric string: ``` curl -X POST -d '{ "textQuery" : "Spicy Vegetarian Food in Sydney, Australia" }' \ -H 'Content-Type: application/json' -H 'X-Goog-Api-Key: API_KEY' \ -H 'X-Goog-FieldMask: places.displayName,places.formattedAddress,places.priceLevel' \ 'https://places.googleapis.com/v1/places:searchText' ``` 2. Click the copy icon in the code sample, ![Select the copy icon.](https://developers.google.com/static/maps/documentation/images/copy-icon.png), to copy the `curl` command. 3. Paste the command in a terminal window and run the command. The response is a JSON object in the form: ```json { "places": [ { "name": "places/ChIJs5ydyTiuEmsR0fRSlU0C7k0", "id": "ChIJs5ydyTiuEmsR0fRSlU0C7k0", "types": [ "vegan_restaurant", "vegetarian_restaurant", "meal_takeaway", "restaurant", "food", "point_of_interest", "establishment" ], "nationalPhoneNumber": "0433 479 794", "internationalPhoneNumber": "+61 433 479 794", "formattedAddress": "29 King St, Sydney NSW 2000, Australia", "addressComponents": [ { "longText": "29", "shortText": "29", "types": [ "street_number" ], "languageCode": "en-US" }, ... } ``` ## Apply API key restrictions > [!CAUTION] > **Caution:** An **unrestricted** API key can be used to make a request to **any** Google Maps Platform service, including the Places API (New). **You are financially responsible > for charges caused by abuse of unrestricted API keys.** Google strongly recommends that you restrict your API keys by limiting their usage to only the APIs and apps that need them. Restricting API keys adds security to your application by protecting it from unwarranted requests. API keys support two types of restrictions: - [API restrictions](https://cloud.google.com/docs/authentication/api-keys#adding-api-restrictions) specify which SDKs and APIs can be called using the API key. The console and the gcloud CLI require at least one API restriction when you create a key. - [Application restrictions](https://cloud.google.com/docs/authentication/api-keys#adding-application-restrictions) specify which websites, IP addresses, or apps can use an API key. For more information about applying restrictions, see [Restrict your API keys](https://developers.google.com/maps/api-security-best-practices.md.txt#restricting-api-keys). ## Create an OAuth token Places API (New) supports OAuth 2.0 for authentication. Google supports common OAuth 2.0 scenarios, such as scenarios for a web server. This document describes how to pass an OAuth token to a Places API (New) call in your development environment. For more information about using OAuth in a production environment, see [Authentication methods at Google](https://cloud.google.com/docs/authentication). You can call Google Maps APIs directly by making API requests to the server, or you can use [client libraries](https://cloud.google.com/apis/docs/client-libraries-explained) to simplify your code. Google Maps provides client libraries for Go, Java, Node.js, and Python. For more information, see [Places API (New) client libraries](https://developers.google.com/maps/documentation/places/web-service/client-libraries.md.txt). ## OAuth overview You can create and manage access tokens with OAuth in several ways depending on your deployment environment. You can use OAuth 2.0 for server-to-server interactions between your application and a Google service. For this scenario, you use a service account that's associated with your application rather than an individual user. You can make API requests using the service account without involving users directly. For more information about authentication methods, see [Authentication methods at Google](https://cloud.google.com/docs/authentication). Alternatively, you can integrate Places API (New) into an Android or iOS mobile app. For more information about using OAuth and managing access tokens for different deployment environments, see [Using OAuth 2.0 to Access Google APIs](https://developers.google.com/identity/protocols/oauth2.md.txt). ## OAuth scopes To use OAuth with Places API (New), you must assign the OAuth token the following scope: https://www.googleapis.com/auth/cloud-platform ## Example: Try REST API calls in your local development environment If you don't have an environment that generates tokens and you want to try Places API (New) with an OAuth token, use the procedure in this section. This example describes how to use the OAuth token provided by [Application Default Credentials (ADC)](https://cloud.google.com/docs/authentication/application-default-credentials) to make the call. For more information about using ADC to call Google APIs with client libraries, see [Authenticate using client libraries](https://cloud.google.com/docs/authentication/client-libraries). Use the following REST procedure only for development or testing, not for production. ### Prerequisites Before you make a REST request using ADC, use the `gcloud` CLI to provide credentials to ADC: 1. Install and initialize the `gcloud` CLI. For more information, see [Install the gcloud CLI](https://cloud.google.com/sdk/docs/install). 2. Authenticate with the `gcloud` CLI: ``` gcloud auth application-default login ``` 3. Complete the sign-in process to save your credentials in the [local credential file used by ADC](https://cloud.google.com/docs/authentication/application-default-credentials#personal). For more information, see [Set up ADC for a local development environment](https://cloud.google.com/docs/authentication/set-up-adc-local-dev-environment). ### Make a REST request In this example, you pass two request headers: - Pass the OAuth token in the `Authorization` header by using the following command to generate the token: [`gcloud auth application-default print-access-token`](https://cloud.google.com/sdk/gcloud/reference/auth/application-default/print-access-token) The returned token has a scope of `https://www.googleapis.com/auth/cloud-platform`. - Pass the ID or name of your Google Cloud project that has billing enabled in the `X-Goog-User-Project` header. To call Places API (New) using an OAuth token, complete the following steps: 1. In the following code sample, replace PROJECT_ID with your Google Cloud project ID: ```json curl -X POST -d '{ "textQuery" : "Spicy Vegetarian Food in Sydney, Australia" }' \ -H "Content-Type: application/json" \ -H "Authorization: Bearer $(gcloud auth application-default print-access-token)" \ -H "X-Goog-User-Project: PROJECT_ID" \ -H "X-Goog-FieldMask: places.displayName,places.formattedAddress" \ "https://places.googleapis.com/v1/places:searchText" ``` 2. To copy the `curl` command, click **Copy** in the code sample. 3. Paste the command in a terminal window, and then run it. The response is a JSON object: ```json { "places": [ { "name": "places/ChIJs5ydyTiuEmsR0fRSlU0C7k0", "id": "ChIJs5ydyTiuEmsR0fRSlU0C7k0", "types": [ "vegan_restaurant", "vegetarian_restaurant", "meal_takeaway", "restaurant", "food", "point_of_interest", "establishment" ], "nationalPhoneNumber": "0433 479 794", "internationalPhoneNumber": "+61 433 479 794", "formattedAddress": "29 King St, Sydney NSW 2000, Australia", "addressComponents": [ { "longText": "29", "shortText": "29", "types": [ "street_number" ], "languageCode": "en-US" }, ... } ``` ### Troubleshooting If your request returns an error message stating that this API doesn't support end-user credentials, see [Troubleshoot your ADC setup](https://cloud.google.com/docs/authentication/troubleshoot-adc).
## What's next Now that you have enabled Places API (New) and configured an API key, see [About the Places API (New)](https://developers.google.com/maps/documentation/places/web-service/op-overview.md.txt) to learn more how to use Places API (New).