Stephen, Understood - if you need to get the CID of the currently logged in user, you would have to make sure that the clientCustomerId element is not included in the request at all. To do this, you have to ensure that no one had set it to an empty string neither via the API nor the auth.ini file.
Rather, you'll have to ensure the value is null, and subsequently, the generated SOAP XML request will not have the clientCustomerId element. Thanks, Ray On Friday, July 25, 2014 3:55:54 PM UTC-4, Stephen Yeargin wrote: > > (Posting this back in context, because it got lost in translation with the > ticketing system.) > > This particular group of users that are authenticating with our platform > are not using an MCC. So, from the API perspective, there is not a > hierarchy. The CustomerService endpoint (as opposed to the > ManagedCustomerService), as recently as v201309, would respond with > information on the currently authenticated user including their Customer > ID. > > I would not need to provide a customer ID to obtain the customer ID. :-) > > - Stephen > > > On Jul 25, 2014, at 1:25 PM, adwords-api@googlegroups.com wrote: > > Stephen, >> >> In the SOAP header, the client customer ID header is empty >> <ns2:clientCustomerId/>. >> This wouldn't work. Are you trying to get the CID of the MCC owning the >> developer token? >> >> Thanks, >> >> >> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ >> Also find us on our blog and discussion group: >> http://googleadsdeveloper.blogspot.com/search/label/adwords_api >> https://developers.google.com/adwords/api/community/ >> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ >> >> On 07/24/14 16:31:18 ste...il.com wrote: >> >> Replied privately. >> >> >> -- >> -- >> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ >> Also find us on our blog and Google+: >> https://googleadsdeveloper.blogspot.com/ >> https://plus.google.com/+GoogleAdsDevelopers/posts >> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ >> >> You received this message because you are subscribed to the Google >> Groups "AdWords 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 Forum" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to adwords-api+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> >> > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords 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 Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
