How does the Token refresh mechanism work?

We don’t refresh Tokens automatically. Developers initiate Token refreshs in these scenarios:

  1. Configure the Token’s validity period in the Developer Console, defaulting to permanent. For subsequent logins, skip requesting a Token from RC. The App Server provides the saved Token directly.

  2. After refreshing the App Secret in the Developer Console, previously obtained Tokens become invalid. Use the new App Secret to generate a signature and retrieve a new Token.

  3. The App Server calls RC’s API to get a Token. For the same User ID, you can retrieve a Token multiple times. Tokens remain valid within their validity period and expire afterward, requiring a new retrieval.