#access_token

[sajadesign]

La plus extraordinaire femme qu'on ait jamais rencontrée est celle qu'on voit un produit saja dans ses 👐 mains #access_token #cosmetics #cosmotic #femme #beauty.

[ktkaran-blog]

https://www.instagram.com/accounts/signup/index/Copy_this_Url/?#access_token=EAABwzLixnjYBAAmPNz3ZAmZC9WKylCTqYJPBgO2xDmxZABu90eKj1ZAMeokHrPgEyZAouAbmgtJxH3N3j16CakCGUzbhp5Yn9MEUZATTRO5lnkRRMaXy4NavNqLZCLAxrvl7A6FgNGyDae4EKOoZBLfxgaTxZBmIpcLoZD&expires_in=5184000&code=AQCG4H0UkRmOl1b-aY3fPY6oVMykCb2AlOGJ3Wb1af1OgnM1qKrLnBffdOxpwp74f2Cq-_KUjsJ1flJAlKWOB5aN2irQnTCs_tYTzGssO0iV1XnlEANLMHsuU22xyWJJTvFHKa0p2k_F3oWz7JfF7kmp-hvAjIIvXFBK83dzLORzVKOQUyE7oKCdwl3G3pitVBIrYLxTZyAKtb-UYS22_Nnt3y6Sf4sXmkanD3ZVcaNHLFPzNtmFkbhOT2GkZ2t1AtZDBiqPB3hJFEQFzaEurX48krGjwbe-Mdo299GFzr6B_oj7WuPZz2ESQW-4JimrD1JTbGia2RUtH2BENV8h5lFe

[jacob-cs]

We have a standalone Java application (see 'Installed application': https://developers.google.com/accounts/docs/OAuth2) which runs periodically and uses google API (updates some informations from

original source : http://stackoverflow.com/questions/13851157/oauth2-and-google-api-access-token-expiration-time

You shouldn't design your application based on specific lifetimes of access tokens. Just assume they are (very) short lived.

However, after a successful completion of the OAuth2 installed application flow, you will get back a refresh token. This refresh token never expires, and you can use it to exchange it for an access token as needed. Save the refresh tokens, and use them to get access tokens on-demand (which should then immediately be used to get access to user data).

EDIT: My comments above notwithstanding, there are two easy ways to get the access token expiration time:

It is a parameter in the response (expires_in)when you exchange your refresh token (using /o/oauth2/token endpoint). More details.

There is also an API that returns the remaining lifetime of the access_token:

https://www.googleapis.com/oauth2/v1/tokeninfo?access_token={accessToken}

This will return a json array that will contain an expires_in parameter, which is the number of seconds left in the lifetime of the token.

[vinh-tran]

Removal of offline_access Permission

Now, the default time for access token is 2 hours. It's not enough for us to do some task that need a long long time. (Ref: http://developers.facebook.com/blog/post/2011/05/13/how-to--handle-expired-access-tokens/)

Since the offline_access is predicated, FB have another end point that help us renew the access token. We can renew it for 60 days and you can do this many time.

Client-side OAuth and Extending Access_Token Expiration Time through New Endpoint

Using the new endpoint below, you will be able to extend the expiration time of an existing, valid access_token. If the access_token was originally generated from a client-side OAuth call or through a signed_request, the endpoint will actually return a new access_token. You should use this new access_token going forward. The original access_token will continue to function until it expires, but again, it will be more effective to use the new access token with the longer expiration time.

To get the access_token simply pass your own client_id (your app_id), your app_secret, and the client-side access_token to the endpoint below. The returned access_token will be set to expire in 60 days. If you would like to renew a still valid access_token, you will have to get a new client-side access token first and then call the same endpoint below. The returned access_token with the newly extended expiration time may or may not be the same as the previously granted extended access_token.

https://graph.facebook.com/oauth/access_token? client_id=APP_ID& client_secret=APP_SECRET& grant_type=fb_exchange_token& fb_exchange_token=EXISTING_ACCESS_TOKEN

Reference: http://developers.facebook.com/roadmap/offline-access-removal/#extend_token