Generates a token for a new subject id. This method can be used to switch between subaccounts.

Rules:

• subject_id must differ from the subject of the supplied refresh token (otherwise -32602) and must identify an active user (otherwise -32602).
• Regular clients can only switch within their own account family (the main account and its subaccounts). A token issued directly for a subaccount cannot switch to the main account or to sibling subaccounts (-32602 on subject_id). Vault subaccounts are rejected with 14049 (vault_subaccount_not_allowed).
• Without scope, the new token inherits the scope of the supplied refresh token. A supplied scope replaces it (it is not merged), and cannot exceed the scope of the refresh token (13403 scope_exceeded). If it contains neither session: nor connection, a session with a generated name is created.
• The new access token's lifetime is counted from the issue time of the supplied refresh token.
• Over WebSocket, the returned access token is also installed on the current connection, so subsequent private requests act as the new subject.
• An invalid, expired or already-replaced refresh token (or one bound to another connection) returns -32602 on refresh_token; session_not_found means the session of the token no longer exists.

📖 Related Articles:

• Fork and Exchange Tokens
• Managing Subaccounts

Try in API console

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