Hi, Having some more details on your config would indeed help. You can send those *only to me* by clicking "Reply to Author" on this message and we can follow up via email from there.
Thanks, Josh, AdWords API Team On Friday, March 14, 2014 11:55:56 AM UTC-4, apiapi wrote: > > Hi Josh. Thanks for the fast response. > > We do in fact require a Service Account, we are not building a "typical" > app that interacts with the API. > > I believe I have done all of the steps and am still getting an error about > the scope permissions. I have notified our enterprise account manager as > well, who is trying to find someone within the API team to assist me. We > have not had a success for ~3 weeks at this point, so could use the help. > > Running the Google-provided sample code with parameters in the app.config, > the error is that the scope is not allowed. As an alternate test, I > purposefully malformed some app.config values and got different and > expected errors, which leads me to beleive that I normal settings are valid > but something else is wrong. > > Looking at GetAccountHierarchy.cs, the code throws on line 78 > "managedCustomerService.get..." > > If there is a way to share some of the app.config bits out of this forum > with you, or some other direct way to test/verify, please let me know. > > Thanks. > > > > On Friday, March 14, 2014 9:51:35 AM UTC-4, Josh Radcliff (AdWords API > Team) wrote: >> >> Hi, >> >> In general we recommend >> (here<https://developers.google.com/adwords/api/docs/guides/service-accounts> >> and >> here<https://developers.google.com/adwords/api/docs/guides/authentication>) >> using >> the *installed application* or *web *flow instead of *service accounts*. >> Service accounts are considerably more complex and not necessary for the >> majority of use cases. A common misconception is that service accounts are >> the only option if you want to be able to access a user's account without >> requiring interaction from the user every time. However, you can still use >> the *installed application* or *web* flow in conjunction with the offline >> access_type<https://developers.google.com/adwords/api/docs/guides/authentication#offline_access> >> for >> this use case. You will have to prompt the user for permissions once, but >> after that you can reuse the *refresh_token* you received for all future >> requests on that account. >> >> If a service account is truly necessary for your use case, please see the >> bottom of the .NET OAuth2 >> page<https://github.com/googleads/googleads-adwords-dotnet-lib/wiki/Using-OAuth> >> and >> confirm that your App.config contains all of the required key/value pairs. >> >> Thanks, >> Josh, AdWords API Team >> >> On Thursday, March 13, 2014 9:25:03 PM UTC-4, apiapi wrote: >>> >>> I downloaded the latest AdWords API v201402 bits, and still receive the >>> same error when simply trying to enumerate the accounts under my MCC using >>> the sample code. I am receiving the same error I got with the 201309-era >>> code. >>> >> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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.
