Hello, we are using exactly the same Oauth token for both the new Google Ads API and the Adwords API the user provided us with when he allowed Adwords API access to his MCC. This access was allowed on the MCC level (4554523147).
I've just executed a GetCustomers call on the Adwords API with exactly the same Oauth token and account we are trying to access (9787711904). It works > <?xml version="1.0" encoding="UTF-8"?> > <SOAP-ENV:Envelope xmlns:SOAP-ENV > ="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:ns1="https://adwords.google.com/api/adwords/mcm/v201809"; > xmlns:ns2="https://adwords.google.com/api/adwords/cm/v201809";> > <SOAP-ENV:Header> > <ns1:RequestHeader> > <ns2:clientCustomerId>6446210156</ns2:clientCustomerId> > <ns2:developerToken>REDACTED</ns2:developerToken> > <ns2:userAgent>.... > </ns2:userAgent> > <ns2:validateOnly>false</ns2:validateOnly> > <ns2:partialFailure>false</ns2:partialFailure> > </ns1:RequestHeader> > </SOAP-ENV:Header> > <SOAP-ENV:Body> > <ns1:getCustomers/> > </SOAP-ENV:Body> > </SOAP-ENV:Envelope> > > <soap:Envelope > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> > <soap:Header> > <ResponseHeader xmlns:ns2 > ="https://adwords.google.com/api/adwords/cm/v201809"; > xmlns="https://adwords.google.com/api/adwords/mcm/v201809";> > <ns2:requestId>00058b38333e45ae0a858ccb460cfe2f</ns2:requestId> > <ns2:serviceName>CustomerService</ns2:serviceName> > <ns2:methodName>getCustomers</ns2:methodName> > <ns2:operations>0</ns2:operations> > <ns2:responseTime>124</ns2:responseTime> > </ResponseHeader> > </soap:Header> > <soap:Body> > <getCustomersResponse xmlns > ="https://adwords.google.com/api/adwords/mcm/v201809"; > xmlns:ns2="https://adwords.google.com/api/adwords/cm/v201809";> > <rval> > <customerId>6446210156</customerId> > ... > </rval> > </getCustomersResponse> > </soap:Body> > </soap:Envelope> On Wednesday, 12 June 2019 21:37:00 UTC+2, adsapiforumadvisor wrote: > > Hello Konstantin, > > Could you please confirm the user using which the OAuth credentials are > generated? In general when using login-customer-id the OAuth user must have > access to the MCC account. > > Regards, > Sai Teja, Google Ads API Team > > ref:_00D1U1174p._5001UBmwT1:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 "AdWords API and Google Ads 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/1a00eada-3739-4e4e-982b-6c8eaf2c37f5%40googlegroups.com.
