Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Postman 403 Error Code Issues when using Google Ads

I created new credentials in Google Developer Console  for Google Ads base  URL : https://googleads.googleapis.com/v14/customers.  and added the scope:   https://www.googleapis.com/auth/adwords .

For Postman I performed the following steps in my Google Ads workspace :

  1. Added Client Id and Client Secret to the variables portion of the Google Ads collection.
  2. Set the token name
  3. set the grant type  = 'Authorization Code'
  4. Callback URL = https://oauth.pstmn.io/v1/browser-callback
  5. Auth URL = https://accounts.google.com/o/oauth2/v2/auth
  6. Access Token URL = https://oauth2.googleapis.com/token
  7. Scope = https://www.googleapis.com/auth/adwords
  8. Refresh token (default) = https://oauth2.googleapis.com/token

When I click Access New Token, I get the redirect page requesting me to choose an account. So I choose my google account and allow oauth.pstmn.io to access my google account (This is postman browser) .

The token generation fails with the message below (note that I have already successfully done token generation with credentials used for DFA Reporting for Campaigns, Sites, and Ads in GCM 360):

However the result is that I get  is an "invalid client".  How could that be since I created the client in Google Developer Console and copied those over to Postman?  Thanks
Here are the error slides:

UnsuccessfulPostman_Token_Generation.pngUnsuccessfulPostman_Token_Generation2.pngUnsuccessfulPostman_Token_Generation3.png

Restricted Scopes  AdWordsRestricted Scopes AdWords

 

Solved Solved
0 1 773
1 ACCEPTED SOLUTION


@Tonanate wrote:

Two really fundamental things that I had forgotten when calling Google Ads whether in Postman OR in an AWS python integration (I cannot believe I missed this !) and they are:

1. Make sure that the client gives you a developer token
2. Make sure that your scope is non-Sensitive or, if the scope is sensitive, has been approved by Google Developer Team to allow the API to access data.

You need both of these to make this work. I was so swayed by the results of the dfareporting scope working for Campaign Manager 360 that I completely forgot the importance of scope sensitivity. Now I'll have to tell the client they must wait anywhere from 3 - 5 days for approval.

 

View solution in original post

1 REPLY 1


@Tonanate wrote:

Two really fundamental things that I had forgotten when calling Google Ads whether in Postman OR in an AWS python integration (I cannot believe I missed this !) and they are:

1. Make sure that the client gives you a developer token
2. Make sure that your scope is non-Sensitive or, if the scope is sensitive, has been approved by Google Developer Team to allow the API to access data.

You need both of these to make this work. I was so swayed by the results of the dfareporting scope working for Campaign Manager 360 that I completely forgot the importance of scope sensitivity. Now I'll have to tell the client they must wait anywhere from 3 - 5 days for approval.

 

Top Labels in this Space