Hi,
Thank you for reaching out to us.
I had to delete your post since API logs posted on the forum. For the reference, you may refer to below without sensitive information:
“Hi there,
It used to work, but lately we are getting the error USER_PERMISSION_DENIED
User doesn't have permission to access customer.
This is the API call Request/Response (I hope you can help us):”
I can see that you have encountered the "USER_PERMISSION_DENIED" which means a user doesn't have permission to access a customer and you’re accessing a client customer using 'login-customer-id’ in the request.
To address the above error, you will need to ensure that the user / email address you used to generate the credentials indeed has access to the account in your request. If the user / email address has access or is associated with the MCC / manager account, you will need to specify the said MCC / manager account ID as the value of the login-customer-id field.
If the issue still persists, you may please provide the user account / email address that you used to generate API access or refresh tokens. With the help of this information, I can check if you set the correct customer ID to login-customer-id.
Best regards,
![]() |
Google Ads API Team |
Hi,
Thanks for getting back with us.
Moving forward to your error about "Customer ID 4822940284 is likely a test account, so its customer client information cannot be retrieved.". Could you confirm if you got this error while running the API call to Get Account Hierarchy while using the customer_client resource? As upon checking on our end the CID 4822940284 has Standard API access and not a test account.
In line with this, for us to further investigate, could you provide us the complete request and response logs with request ID generated as shown in the respective links.
You may then send the requested logs via the Reply privately to author option. If the reply privately option is not available, you can send your logs directly to our googleadsa...@google.com alias instead.
Regards,
Hi,
Thank you for getting back to us.
I see that you have posted the full logs on this forum and it is not recommended. With this, I had to delete your recent post. Moving forward to your concern, you will need to ensure that the user / email address you used to generate the credentials indeed has access to the account in your request.
Let me know how it goes on your end if this resolves your issue and if the issue persists, then you may provide to us the updated complete request and response logs with the request-id generated once again along with the email address used to generate the OAuth credentials from your end so we can check on this email address if it has access to the account in question.
You can provide these via the Reply privately to author option. If this option is not available, then send it instead on this email address googleadsa...@google.com.
Regards,