> ## Documentation Index
> Fetch the complete documentation index at: https://docs.argyle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Link token renewal

> Refreshing a Link session will require a token for the same user.

October 29, 2026
Link
API
Breaking

![Link update illustration](https://mintcdn.com/argyle/spW0uZwUC4bDyMgL/images/changelog-generic/link.png?fit=max\&auto=format\&n=spW0uZwUC4bDyMgL\&q=85\&s=b6ea923ffd5a9eaa46c5b7425326d751)

Starting **November 30, 2026**, a [user token](https://docs.argyle.com/link/user-tokens.md) will no longer be usable to refresh a different user’s Link session. Using a token for a different user will return an `invalid_user_token` error.

When a user token expires (or five minutes before expiration on Web), the `onTokenExpired` [callback](https://docs.argyle.com/link/reference/callbacks.md#ontokenexpired) is triggered. It provides an update function for replacing the current session’s token without closing and re-initializing Link.

Alternatively, you can create a new user token for existing users through the API’s [create a user token endpoint](https://docs.argyle.com/api-reference/user-tokens/create-a-user-token.md) and use the returned token to initialize a new Link session. When refreshing a token, use the existing user.

*If your token refresh flow already uses the same user, no changes are required.*