Standard API token requests with no answer for 6 weeks

73 views
Skip to first unread message

Coverler Admin

unread,
Nov 30, 2023, 9:13:04 PM11/30/23
to Google Ads API and AdWords API Forum
Hi,

Like tens of people below me in this forum I also've been trying to get an API for 6 weeks now, and got nothing back at all. I've filled out both the request form and the compliance form to request a status update multiple times, I even contacted my local Ads managers to help – but still nothing. 
Are those forms even working and is anyone actually getting basic API keys at the moment? 

Seeing what the standard answer to requests is – here is my answer upfront: 
  • MCC ID: 521-681-8186
  • No case ID was generated
  • Basic level requested
Thanks
Dasha

Google Ads API Forum Advisor

unread,
Dec 1, 2023, 5:09:33 AM12/1/23
to ads-api-compl...@google.com, adwor...@googlegroups.com
Hi,

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

After reviewing your concern, I understand that you have applied for basic access and haven’t received any response. Since the access requests are handled by the Google Ads API Compliance team, we are transferring the case to the Ads API Compliance team. 

@Compliance team, please confirm if you are able to assist in the below access request.

Summary:

The user has applied for basic access with the below details.
  • Google Ads Manager Account (MCC) ID: 521-681-8186
  • Case ID: The user has not received any case ID.
Do reach out to the Google Ads API support team for any queries related to the API.
 
This message is in relation to case "ref:!00D1U01174p.!5004Q02qW0wJ:ref"

Thanks,
 
Google Logo Google Ads API Team


Coverler Admin

unread,
Dec 5, 2023, 1:35:38 AM12/5/23
to Google Ads API and AdWords API Forum
Hey, I have a correction
  • Correct Google Ads Manager Account (MCC) ID: is 245-245-6952
  • 521-681-8186 is the Google Ads Account we are desperately trying to get the token for
  • We still applied from the correct account is only MCC allows to request tokens.. 
Sorry for the mistake and hopefully that can be resolved soon. 
Reply all
Reply to author
Forward
0 new messages