OAuth Playground

Another option for generating OAuth2 credentials is to use the OAuth2 Playground. The OAuth2 Playground, in conjunction with the Google API Console, allows you to manually create OAuth2 tokens.

Prerequisites

Before creating credentials, you need to create a project, configure your user consent screen, and enable the AdMob API.

Get a client ID and client secret

Create a credential

Key Point: To use the OAuth2 Playground, you need to generate a client ID for a web application. This is the only type of application that will work with the OAuth2 Playground.

1. Open the Google API Console Credentials page.

2. From the project drop-down, select an existing project or create a new one.

   Key Point: Create a project with a unique identifying name for each shared token, so you can share or revoke them easily.

3. On the Credentials page, select Create credentials, then select OAuth client ID.

4. Under Application type, choose Web application.

5. Under Authorized redirect URIs, add a line with: https://developers.google.com/oauthplayground

   Key Point: If you have an existing credential, you can reuse it by setting the Authorized redirect URIs as above.

6. Click Create.

7. On the Client ID page, take note of the client ID and client secret. You'll need these in the next step.

Configure an OAuth consent screen

You must configure an OAuth consent screen before using an OAuth 2.0 client ID.

1. Open the Google API Console Consent Screen page.

2. From the project drop-down, select the same project used to generate the credential.

3. Configure your OAuth consent screen to use your OAuth 2.0 client ID. There are multiple ways to do this:

   1. Set your user type to External and publishing status to Published.
   2. Or, set your user type to External and publishing status to Testing, then add Test users by selecting add users to give them access to use your OAuth 2.0 client ID.

See additional information on setting up your OAuth consent screen.

Generate tokens

Key Point: The Google user you're signed in as in your browser determines which AdMob account you'll be able to access with the OAuth2 credentials you generate. Therefore, you may want to do these steps in an incognito window or when you're not signed in to your Google account, since it's likely that the user whose credentials you want to use isn't the same user you were signed in as when you got the client ID and secret.

1. Go to the OAuth2 Playground, (using this link should pre-populate some key values for you).

2. Click the gear icon in the upper right corner and check the box labeled Use your own OAuth credentials (if it isn't already checked).

3. Make sure that:

   • OAuth flow is set to Server-side.
   • Access type is set to Offline (this ensures you get a refresh token and an access token, instead of just an access token).

4. Enter the OAuth2 client ID and OAuth2 client secret you obtained above.

   

5. In the section labeled Step 1 - Select & authorize APIs, enter the following URL in the text box at the bottom, if it's not already there, then click Authorize APIs:

   https://www.googleapis.com/auth/admob.readonly

6. If prompted, sign in to the account to which you want to grant access and authorization. Otherwise, confirm that the current Google user in the top right corner is the AdMob account for whom you want to obtain credentials.

   Key Point: If you got your client ID and secret only a few minutes ago, and you get an error such as Error: redirect_uri_mismatch, it's possible the changes you made haven't yet propagated. Click your browser's back button, wait a few minutes, then try clicking Authorize APIs again.

7. A prompt appears indicating your app would like to See your AdMob data. Click Accept to continue.

8. In the tab labeled Step 2 - Exchange authorization code for tokens, an Authorization code should appear. Click Exchange authorization code for tokens.

   

9. If all goes well, the Refresh token and Access token should be filled in for you (you may have to re-expand Step 2 - Exchange authorization code for tokens):

   

10. Copy the Refresh token into the configuration file for your client library of choice, along with the client ID and client secret.

11. Configure a client library for OAuth in the AdMob API.

Remove the OAuth2 Playground from your client ID

Now that you have a refresh token, you no longer need the OAuth2 Playground to be an authorized redirect URI. To remove it from the list of authorized redirect URIs:

1. Go to the Google API Console Credentials page.

2. From the project drop-down, select your project.

3. On the Credentials page, click the client ID name to edit.

4. Remove https://developers.google.com/oauthplayground from the Authorized redirect URIs. Note that you must leave at least one redirect URI in place.

5. Click Save.

Revoke shared tokens

You can revoke shared tokens in two ways:

1. Navigate to your Google account permissions page and revoke access from the relevant project.

2. Alternatively, you can revoke web application tokens using the Google Identity API.