I was experiencing a similar issue...
Here is what i found regarding similar error message :
{ "message": "The caller does not have permission", "code": 7, "status":
"PERMISSION_DENIED", "details": [ { "@type":
"type.googleapis.com\/google.ads.googleads.v15.errors.GoogleAdsFailure",
"errors": [ { "errorCode": { "authorizationError": "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"
} ], "requestId": "UAo0n2LRjzMd8HJjKdc4rw" } ] }
-- This did not actually appear to be an issue with the login-customer-id
NOT being in the header...
the issues that resolved this for me was to remove setting the
"linkedCustomerId" from the client which possibly only worked before for
the wrong reasons..
Previously had the client setting the Manager account id as the login
customer id, and the context account was used to set the linkedCustomerId (
which was probably not needed anyways since the requests would contain the
customerId anyways..
Hope this helps.. at least this is what worked for me..
Ricky C
On Wednesday, February 7, 2024 at 7:25:09 PM UTC-6 Google Ads API Forum
Advisor wrote:
> Hi,
>
> Thank you for getting back to us.
>
> The provided logs are partial, which means there is no complete request
> body presented. From the provided logs, we are not sure which service
> you're utilizing to make API calls and are not sure what your request
> header parameters are. Please note that logs are crucial to addressing your
> issue in this context, as we can find complete request and response bodies
> in the logs.
>
> So as requested earlier, please provide us with 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. So that we can address your issue more accurately.
>
> Kindly note that you have to enable logging if you are using a client
> library. You can refer to the guides in PHP
> <https://developers.google.com/google-ads/api/docs/client-libs/php/logging>
> to
> enable logging at your end. For REST interface requests, you can enable
> logging via the curl command by using the -i flag.
> This message is in relation to case "ref:!00D1U01174p.!5004Q02rYS7v:ref"
>
> 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/c48eec03-41d5-4852-8676-e14d1bac549an%40googlegroups.com.
