Refresh login_identity_token
Generate a new login_identity_token and login_identity_refresh_token using a valid login_identity_refresh_token.
This only refreshes the Customer App’s ability to authenticate with Finverse’s API — it does not refresh or modify any end-user data associated with the Login Identity. To request instead Finverse to retrieve new data from connected institutions, please use the POST requests under “Data Refresh”.
Authorization: customer_token
Token handling
Storage
login_identity_token and login_identity_refresh_token are highly sensitive since they are needed to retrieve data on each Login Identity.
Best practices:
* Securely store each token in your back-end
* Never disclose these tokens externally (e.g. in your front-end).
Renewal
login_identity_token expires after 1 hour. login_identity_refresh_token expires after 90 days.
Repeat this request for token renewal.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Body
The refresh token
Login Identity refresh token (referred to as login_identity_refresh_token) generated during the initial linking session (e.g. POST /auth/token) or during a subsequent token refresh request (POST /auth/token/refresh). Note: this request invalidates the refresh_token submitted. Use the refresh_token returned in the response for subsequent refresh requests.
Response
New refresh, access token
(SENSITIVE) Login Identity access token (referred to as login_identity_token).
Access token validity length (in seconds).
Access token issue time
Finverse Login Identity ID for this Login Identity. Always unique. Linking the same account at the same institution twice will result in two Login Identities with different IDs (use Refresh/Relink methods to refresh data for a Login Identity without updating the ID).
(SENSITIVE) Login Identity refresh token (referred to as login_identityrefresh_token)
Possible values: Bearer