Thanks for the confirmation, explains my issues with OAuth2 and long lived
tokens.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Hi David,
OAuth2 does not have long-lived OAuth tokens. It has short-lived access
tokens that can be refreshed using the refresh token as needed. OAuth 1
does allow for long-lived access tokens. Note that we've not yet tested
OAuth2 support with the AdWords API.
The OAuth playground may be
Thanks for the reply Kevin. I've reviewed the docs you've referenced, and
could not find the method to generate a long-lived access token - one that
does not require continued refresh token exchanges. I was looking for an
interactive panel to perform the OAuth2 dance; after completing I would
Hi David,
The client libraries (except for java) have published code examples
showing how to use the libraries to do this. For example, see here for
python:
http://code.google.com/p/google-api-ads-python/source/browse/trunk/examples/adspygoogle/adwords/other/use_oauth.py
We published a blog
While attending the API WorkShop in NYC, one of the Google team was
discussing a method for returning a long lived access token for the
AdWords API scope, to use for Reporting. One could then store in DB
and present in place of the OAuth "dance" flow to obtain the token.
I've gone through the work
