Unable to Add Test Users or Complete OAuth Consent Screen for Google Ads API

57 views
Skip to first unread message

Radha Gautam

unread,
Jul 22, 2025, 8:55:34 AMJul 22
to Google Ads API and AdWords API Forum
  I am attempting to authenticate with the Google Ads API using OAuth 2.0 and Postman. I have created a Google Cloud project, enabled the Google Ads API, and configured the OAuth consent screen with the "External" user type. However, after saving the app information, I am not able to proceed to the Scopes or Test Users sections. The interface redirects me to the overview page without presenting the steps to add test users or configure scopes. Due to this, I cannot add my Gmail account as a test user, and when I attempt to obtain an access token through Postman using the redirect URI https://oauth.pstmn.io/v1/callback, I encounter the error: “Access blocked: oauth.pstmn.io has not completed the Google verification process.” This is preventing me from generating the access token required to interact with the API. Please assist in resolving the issue with the OAuth consent screen setup.  

Google Ads API Forum Advisor

unread,
Jul 22, 2025, 12:01:45 PMJul 22
to gautamr...@gmail.com, adwor...@googlegroups.com
Hi,

Thank you for reaching out to the Google Ads API support team.

We recommend that all apps undergo the Google OAuth verification process as soon as possible to avoid any business interruptions. As stated in this document the verification is independent and in addition to any reviews conducted as part of the developer token approval process, and is required since the Google Ads API scope is a sensitive scope

Note that OAuth verification is outside the scope of the Google Ads API team, as our team can only assist with technical queries or concerns related to the Google Ads API. I would recommend that you reach out to the GCP product support team via this link.  

Thanks,
 
Google Logo Google Ads API Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5
[2025-07-22 16:00:49Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01swMGX:ref" (ADR-00319753)



Radha Gautam

unread,
Jul 22, 2025, 1:46:46 PMJul 22
to Google Ads API and AdWords API Forum

Ao Smith Service

unread,
Jul 22, 2025, 3:07:31 PMJul 22
to adwor...@googlegroups.com


Arman

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
 
You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwor...@googlegroups.com
To unsubscribe from this group, send email to
adwords-api...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
---
You received this message because you are subscribed to the Google Groups "Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/adwords-api/T4x3n000000000000000000000000000000000000000000000SZT5TD00eiWWHRuiSbGgaRDPXXMB9w%40sfdc.net.

Google Ads API Forum Advisor

unread,
Jul 22, 2025, 6:37:22 PMJul 22
to gautamr...@gmail.com, adwor...@googlegroups.com
Hi,

I understand that you are encountering a problem with the app verification process on the OAuth consent screen. As mentioned earlier, I would recommend you kindly refer to the “Google OAuth verification” documentation for more information. You can refer to this guide in adding scopes in the GCP console. If you still encounter any issues related to the OAuth, I would recommend you kindly reach out to the GCP Product support team as they are better equipped to address your concerns. Our team can only help you with technical queries or concerns related to the Google Ads API.


Thanks,
 
Google Logo Google Ads API Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5

[2025-07-22 22:36:38Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01swMGX:ref" (ADR-00319753)



Reply all
Reply to author
Forward
0 new messages