We don’t refresh Access Tokens automatically. Developers initiate Access Token refreshes in these scenarios:
-
Configure the Access Token’s validity period in the Console, defaulting to permanent. For subsequent logins, skip requesting a Access Token from Nexconn. The App Server provides the saved Access Token directly.
-
After refreshing the App Secret in the Console, previously obtained Access Tokens become invalid. Use the new App Secret to generate a signature and retrieve a new Access Token.
-
The App Server calls Nexconn API to get an Access Token. For the same User ID, you can retrieve a Access Token multiple times. Access Tokens remain valid within their validity period and expire afterward, requiring a new retrieval.
