Version: 5.1.1
Authorization Code
This way is not recommended for client-side apps and requires server-side code to run securely. With this approach, you first get a code which you need to trade against the access-token. In this exchange you need to provide your Client-Secret and because of that it's not recommended. A good thing about this method: You can always refresh your token, without having the user to auth it again.
More info: here
#
Token RefreshOnce the AccessToken
is expired, you can use your RefreshToken
to get a new one.
In this procedure, no HTTP Server is needed in the background and a single HTTP Request is made.