Generates a token for a new named session. This method can be used only with session scoped tokens.

Rules:

• The refresh token must have session scope; a connection scope refresh token is rejected with -32602 on refresh_token.
• session_name longer than 64 bytes is truncated (not rejected). The truncated name must differ from the current session name, otherwise the call fails with -32602 on session_name.
• The forked session keeps the scope of the original token with only the session name replaced, and receives a fresh access token and refresh token.
• Unlike public/auth and public/exchange_token, the forked access token is not installed on the current WebSocket connection: the connection keeps its current authentication until you authenticate it with the new token.
• An invalid, expired or already-replaced refresh token returns -32602 on refresh_token; session_not_found means the session of the token no longer exists.

📖 More Details: Fork and Exchange Tokens

Try in API console

{
  "result": {
    "access_token": "843SehgeX5n6XxEU4XbABx4Cny5Akai5iHiJePTsvUw7",
    "expires_in": 900,
    "refresh_token": "6faf8L36JdaSqsjCEEiwqifPpj6JB18RWwiWHrsGTZ91"
  }
}