Configure the Google API Console project

Note: The current step of this tutorial depends on the type of application you are building. We strongly recommend using a service account to make API calls. However, the user authentication option is also provided as an alternative. The rest of this tutorial will be customized based on your choice.

Service accounts User authentication

Configure the OAuth consent screen

When you use OAuth 2.0 for authorization, Google displays a consent screen to the user including a summary of your project, its policies, and the requested authorization scopes of access. Configuring your app's OAuth consent screen defines what is displayed to users and app reviewers, and registers your app so you can publish it later.

Follow the instructions to configure an OAuth consent screen for your application and add https://www.googleapis.com/auth/adwords as an OAuth scope.

Create a client ID and client secret

Note: If you are already using another Google API and have created an OAuth 2.0 client ID and client secret, you can skip this step and reuse the existing credentials.

You can skip this step if you're using an existing Google API Console project that already has a generated client ID and client secret. Otherwise, create a client ID and client secret by following the instructions. You may choose either Desktop app or Web application as the application type. Once you create the OAuth 2.0 client, download the client's JSON file by first clicking its Download OAuth client icon and then the DOWNLOAD JSON button on the following screen.