Yep, I know. But I have linked MCC account to the customer account  

This is completed API logs: 

*Method: /google.ads.googleads.v16.services.GoogleAdsService/Search*

*Host: googleads.googleapis.com*

*Headers: {*

*  "developer-token": "REDACTED",*

*  "login-customer-id": "4374963390",*

*  "x-goog-api-client": "gl-python/3.10.12 grpc/1.64.0 gax/2.19.0 
gccl/24.0.0 pb/4.25.3",*

*  "x-goog-request-params": "customer_id=5709969314"*

*}*

*Request: customer_id: "5709969314"*

*query: "\n            SELECT\n              customer_client.id,\n          
    customer_client.descriptive_name,\n              
customer_client.manager,\n              customer_client.currency_code\n    
        FROM customer_client where customer_client.manager = false\n        
    "*

*Response*

*-------*

*Headers: {*

*  "google.ads.googleads.v16.errors.googleadsfailure-bin": 
"\n\u0001\n\u0002H\u0002\u0012\u0001User doesn't have permission to access 
customer. Note: If you're accessing a client customer, the manager's 
customer id must be set in the 'login-customer-id' header. See 
https://developers.google.com/google-ads/api/docs/concepts/call-structure#cid\u0012\u0016F5TRUr_VwHYT6EW5FcBEFQ",*

*  "grpc-status-details-bin": "\b\u0007\u0012#The caller does not have 
permission\u001a\u0002\nDtype.googleapis.com/google.ads.googleads.v16.errors.GoogleAdsFailure\u0012\u0002\n\u0001\n\u0002H\u0002\u0012\u0001User
 
doesn't have permission to access customer. Note: If you're accessing a 
client customer, the manager's customer id must be set in the 
'login-customer-id' header. See 
https://developers.google.com/google-ads/api/docs/concepts/call-structure#cid\u0012\u0016F5TRUr_VwHYT6EW5FcBEFQ",*

*  "request-id": "F5TRUr_VwHYT6EW5FcBEFQ"*

*}*

*Fault: errors {*

*  error_code {*

*    authorization_error: USER_PERMISSION_DENIED*

*  }*

*  message: "User doesn\'t have permission to access customer. Note: If 
you\'re accessing a client customer, the manager\'s customer id must be set 
in the \'login-customer-id\' header. See 
https://developers.google.com/google-ads/api/docs/concepts/call-structure#cid"*

*}*

*request_id: "F5TRUr_VwHYT6EW5FcBEFQ"*
And can you check with some 
request_id: yXcGOV9UvWHQM6BkKFxBTA, q00JIVm3B4Lb8-plFRRg5Q 
And you might also missed point I have mentioned, it shows up occasionally. 
Hope you will response soon. Thanks
On Monday, August 26, 2024 at 12:59:08 PM UTC+7 Google Ads API Forum 
Advisor wrote:

> Hi,
>
> It appears that you might have missed our previous response.
>
> The 'USER_PERMISSION_DENIED 
> <https://developers.google.com/google-ads/api/reference/rpc/v17/AuthorizationErrorEnum.AuthorizationError#user_permission_denied>'
>  
> error occurs when the MCC account is not linked to the customer account 
> from which the API request is being made. To resolve this, ensure that your 
> customer account is correctly linked to the appropriate MCC account and 
> that the developer token used in the API calls is valid. Another potential 
> cause is that the email ID used to generate the OAuth credentials is not 
> listed as having 'Admin' or 'Standard' access in your customer account. 
> Kindly verify this by checking under your Google Ads account  > Admin > 
> Access and Security > Users > The email ID has the necessary access level.
>
> Note that you haven't shared the complete API logs as it doesn't contain 
> the request body and the request ID. So, I would request you to share the 
> complete API logs (request 
> <https://developers.google.com/google-ads/api/docs/concepts/field-service#request>
>  and response 
> <https://developers.google.com/google-ads/api/docs/concepts/field-service#response>
>  with request-id 
> <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id>
>  and request header 
> <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers>)
>  
> generated at your end to better assist you further. 
>
>
> You can send the details via *Reply **privately** to the author option*, 
> or *direct **private** reply* to this email.
>
>   
> This message is in relation to case 
> "ref:!00D1U01174p.!5004Q02vFBpm:ref" (ADR-00264154)
>
> Thanks,
>   
> [image: Google Logo] Google Ads API Team 
>
>  
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/de2b4bd1-8ae2-496d-822d-8ec99965758bn%40googlegroups.com.
  • Ma... Nguyen Vien
    • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
      • ... Nguyen Vien
        • ... Nguyen Vien
          • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
            • ... Nguyen Vien
              • ... Nguyen Vien
                • ... Nguyen Vien
                • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
                • ... Nguyen Vien
                • ... Nguyen Vien
                • ... Nguyen Vien
                • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
    • ... Li Tom

Reply via email to