Hi Ajit, Here's our login customer Id guide and migration guide.
Any account returned by Get Account Hierarchy when you you don't specify manager ID and login customer ID can be accessed by your refresh token you used to make the API call. Any account returned by List Accessible Accounts when using a specific refresh token doesn't need the login customer Id. Another property of those accounts returned by List Accessible Accounts is they are the only accounts that can be a login customer Id for the specific refresh token making the API call. A visual way to explain this is to imagine that the same Google account that generated the refresh token was to access an account in the Ads UI. They will see all the the accounts that List Accessible Accounts returns in the top right drop down list when you click the circle representation of the user in the UI. These are accounts the user has direct access to. If an account in that list is an MCC with child accounts attached, then to see the child accounts you would select that MCC in the top right of the UI and then the child accounts are accessible in the top left - middle accounts drop down list box in the UI. These are the same accounts that Get Account Hierarchy shows. To access accounts that are in the top left - middle accounts drop down list box via the API you would put the selected account in the top right list in the UI as login customer Id, and you would put the selected account in the top left - middle accounts drop down list box as the operating customer. In light of the above, if you are still experiencing this error, could you send us a 'DEBUG' log level request and response log of raw API communications returning this error, combined with the Google Account that generated the refresh token used? The request and response appears similar to the JSON Mappings in our REST documentation with additional headers and information such as request Id. Here are logging instructions for our Java, .NET, PHP, Python, Ruby and Perl Ads API Client Libraries. If you are using our REST interface then the full multi line curl command line is a request log and adding curl command line option '-i' will also generate a response log. You may send the requested information via "Reply to author" or via googleadsapi-supp...@google.com with a link to this forum post added to the new thread. Regards, Aryeh Google Ads API Team ref:_00D1U1174p._5001USwXi1: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 "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/x_aNz000000000000000000000000000000000000000000000RDMM5700s5j1kRZ-QkiWS2UgFFtGWw%40sfdc.net.
