By Sai

2015-08-18 15:24:08 8 Comments

I am trying to access Proximity Google API using Postman chrome app. I have followed tutorials on postman and google dev website but I'm still getting 401 error message.

What am I doing?

  • Step 1 - Enable Proximity API:

In order to use Proximity API, it has to be first enabled in Google Dev console. Using this tutorial I have enabled support for Proximity API for my project

  • Step 2 - Get the credentials:

According to this tutorial, I need to get client ID and secret. This is where I am confused. Credentials->Add credentials->OAuth2.0 client ID->select Chrome App radio button (since I am using Postman)->enter last part of Postman's Chrome Web store URL [which is fhbjgbiflinjbdggehcddcbncdddomop]->hit create button These steps will only generate a client ID, not a I doing something wrong?

From the Google Dev console, one can download an JSON file which has client id, auth URI and Token URI enter image description here

I downloaded this but this is of little help if I am using Postman. I am guessing this JSON file is something that can be included in a JS application.

  • Step 3 - Use Postman to test the API

enter image description here

What am I getting? enter image description here

And, once I click on the debug URL, I see the following screen

enter image description here


@DimaTX 2018-11-28 23:13:44

Postman will query Google API impersonating a Web Application

Generate an OAuth 2.0 token:

  1. Ensure that the Google APIs are enabled
  2. Create an OAuth 2.0 client ID

    • Go to Google Console -> API -> OAuth consent screen
      • Add to the Authorized domains. Click Save.
    • Go to Google Console -> API -> Credentials
      • Click 'Create credentials' -> OAuth client ID -> Web application
        • Name: 'getpostman'
        • Authorized redirect URIs:
    • Copy the generated Client ID and Client secret fields for later use
  3. In Postman select Authorization tab and select "OAuth 2.0" type. Click 'Get New Access Token'

    • Fill the GET NEW ACCESS TOKEN form as following
      • Token Name: 'Google OAuth getpostman'
      • Grant Type: 'Authorization Code'
      • Callback URL:
      • Auth URL:
      • Access Token URL:
      • Client ID: Client ID generated in the step 2 (e.g., '')
      • Client Secret: Client secret generated in the step 2 (e.g., 'ABRACADABRAus1ZMGHvq9R-L')
      • Scope: see the Google docs for the required OAuth scope (e.g.,
      • State: Empty
      • Client Authentication: "Send as Basic Auth header"
    • Click 'Request Token' and 'Use Token'
  4. Set the method, parameters, and body of your request according to the Google docs

@Gennadiy Ryabkin 2019-01-28 10:40:24

Detailed, awesome job. It worked for me

@Gennadiy Ryabkin 2019-01-28 10:40:46

More thoroughly explained than by Google's employees :)

@Pierre 2019-04-29 01:41:08

Great works perfectly. Thanks

@ptim 2019-04-30 05:06:36

If using the Insomnia client, then both the Authorized Domain and Redirect URI are Ref:

@irmalcol 2018-07-18 21:39:55

This is an old question, but it has no chosen answer, and I just solved this problem myself. Here's my solution:

  1. Make sure you are set up to work with your Google API in the first place. See Google's list of prerequisites. I was working with Google My Business, so I also went through it's Get Started process.

  2. In the OAuth 2.0 playground, Step 1 requires you to select which API you want to authenticate. Select or input as applicable for your case (in my case for Google My Business, I had to input into the "Input your own scopes" input field). Note: this is the same as what's described in step 6 of the "Make a simple HTTP request" section of the Get Started guide.

  3. Assuming successful authentication, you should get an "Access token" returned in the "Step 1's result" step in the OAuth playground. Copy this token to your clipboard.

  4. Open Postman and open whichever collection you want as necessary.

  5. In Postman, make sure "GET" is selected as the request type, and click on the "Authorization" tab below the request type drop-down.

  6. In the Authorization "TYPE" dropdown menu, select "Bearer Token"

  7. Paste your previously copied "Access Token" which you copied from the OAuth playground into the "Token" field which displays in Postman.

  8. Almost there! To test if things work, put into the main URL input bar in Postman and click the send button. You should get a JSON list of accounts back in the response that looks something like the following:

        "accounts": [
                "name": "accounts/REDACTED",
                "accountName": "REDACTED",
                "type": "PERSONAL",
                "state": {
                    "status": "UNVERIFIED"
                "name": "accounts/REDACTED",
                "accountName": "REDACTED",
                "type": "LOCATION_GROUP",
                "role": "OWNER",
                "state": {
                    "status": "UNVERIFIED"
                "permissionLevel": "OWNER_LEVEL"

@Sai 2015-08-20 20:29:08

I figured out that I was not generating Credentials for the right app type.
If you're using Postman to test Google oAuth 2 APIs, select
Credentials -> Add credentials -> OAuth2.0 client ID -> Web Application.

enter image description here

@Mohammed Almusaddar 2017-01-13 22:31:11

  1. go to
  2. create web application credentials.

Postman API Access

  1. use these settings with oauth2 in Postman:

SCOPE = https: //

post https: //

  "fields": [
      "fieldName": "role",
      "fieldType": "STRING",
      "multiValued": true,
      "readAccessType": "ADMINS_AND_SELF"
  "schemaName": "SAML"
  1. to patch user use:


PATCH[email protected]

  "customSchemas": {
     "SAML": {
       "role": [
          "value": "arn:aws:iam::123456789123:role/Admin,arn:aws:iam::123456789123:saml-provider/GoogleApps",
          "customType": "Admin"

@Matt D 2018-08-09 17:03:43

this doesnt work.

@Vijay Madhavapeddi 2016-12-06 19:36:47

The best way I found so far is to go to the Oauth playground here:

  1. Select the relevant google api category, and then select the scope inside that category in the UI.
  2. Get the authorization code by clicking "authorize API" blue button. Exchange authorization code for token by clicking the blue button.
  3. Store the OAuth2 token and use it as shown below.

In the HTTP header for the REST API request, add: "Authorization: Bearer ". Here, Authorization is the key, and "Bearer ". For example: "Authorization: Bearer za29.KluqA3vRtZChWfJDabcdefghijklmnopqrstuvwxyz6nAZ0y6ElzDT3yH3MT5"

@manasouza 2018-05-26 14:35:54

This workflow resolved my problem! Just to complement the explanation, after "Exchange authorization code for token" I copied the value at "Access token" field and used it as Authorization Bearer on Postman

Related Questions

Sponsored Content

8 Answered Questions

[SOLVED] How to make calls to Twitter API using Postman client

  • 2015-08-23 20:46:56
  • learner
  • 26696 View
  • 50 Score
  • 8 Answer
  • Tags:   twitter postman

8 Answered Questions

[SOLVED] How does OAuth 2 protect against things like replay attacks using the Security Token?

  • 2011-01-18 17:44:59
  • William Jones
  • 232660 View
  • 546 Score
  • 8 Answer
  • Tags:   oauth-2.0

3 Answered Questions

[SOLVED] Postman Oauth 2 callback url - Chrome App

12 Answered Questions

[SOLVED] Is there a link to the "latest" jQuery library on Google APIs?

3 Answered Questions

[SOLVED] Could not obtain Google oAuth 2 token on POSTMan

1 Answered Questions

6 Answered Questions

[SOLVED] Google APIs Console - missing client secret

  • 2012-07-02 14:27:34
  • Alexandru Circus
  • 43293 View
  • 29 Score
  • 6 Answer
  • Tags:   oauth-2.0

3 Answered Questions

[SOLVED] client secret in OAuth 2.0

1 Answered Questions

1 Answered Questions

[SOLVED] POSTMAN, OAuth2 and Google Directory API

Sponsored Content