I am in a similar situation to Joey's. I took your advice and tried to follow the web server flow.
However, it doesn't appear that the AdWords API is supported. I experimented with different "scope" parameter values and all were invalid. Could you please 1) confirm that it is possible to use the web server flow for AdWords; 2) if so, advise the appropriate "scope" parameter value for the URL? Thanks, Becky On Sunday, February 3, 2013 10:56:50 PM UTC-5, Anash P. Oommen (AdWords API Team) wrote: > > Hi Joey, > > Since you have a web application, I'd recommend the web server flow > instead. The main difference from installed application flow is that since > your website can provide a valid callback url, the oauth2 server will > redirect the user directly to this url with the authorization code as part > of the url and hence they don't have to copy-paste the authorization code > into your app. > > See https://developers.google.com/accounts/docs/OAuth2WebServer for > details. If you want to keep the tokens in your database for offline > access, make sure you do offline=true when making the oauth2 access token > request. > > Cheers, > Anash P. Oommen, > AdWords API Advisor. > > On Saturday, February 2, 2013 12:39:34 AM UTC+5:30, Joey Muller wrote: >> >> Hi David, >> >> With the installed applications flow, do users need to copy and paste an >> authorization code into our app if we're using oauth2? My developer thinks >> so. I thought I read otherwise. >> >> Thanks, >> Joey >> >> On Friday, November 16, 2012 3:58:56 PM UTC-8, David Torres wrote: >>> >>> Hi Joey, >>> >>> Our recommendation, moving forward is to use OAuth2. I recommend you >>> looking at the installed applications flow, in which a single user >>> interaction is required to authorize your application access to their >>> account and will grant you a refresh token - that never expires - that your >>> scheduler can re-use to authorize requests. >>> >>> Using OAuth2 will ensure a longer-life to your application in terms of >>> authorization as opposed to ClientLogin which we have already marked as a >>> deprecated authorization method. >>> >>> Best, >>> >>> - David Torres - AdWords API Team >>> >>> On Wednesday, November 14, 2012 2:55:54 PM UTC-5, Joey Muller wrote: >>>> >>>> I have developed a tool for my agency's internal clients. It uses a >>>> scheduler to send automatica emails containing AdWords data. Now, some >>>> other folks are interested in using this, but their AdWords accounts are >>>> not linked to our MCC. What would be the best way to handle this? Would I >>>> use a sign-on or authentication process using oAuth? Or would I store >>>> email >>>> and password combinations in a database and use ClientLogin? I recall >>>> third >>>> party PPC platforms like Marin and others use the email/password combo >>>> solution, but I'm wondering if there is something slicker. >>> >>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/groups/opt_out.
