Possible extend outcomes

When successfully calling connections/extend, you will receive a response back that includes action_needed. This will direct any further action required on the end-user’s part to extend the connection.

No action needed

If connections/extend returns action_needed: "no_action_needed", then the connection has been extended and is able to be used until consent needs to be re-confirmed in the future. The response will also return an updated access_token and refresh_token.

Authentication Needed

If connections/extend returns action_needed: "authentication_needed", then the connection also requires the End-User to go through bank authentication. The response will return a user_input_link that you can direct the user toward. Upon successful bank authentication, you will receive a webhook notification to the redirect_uri specified when calling connections/extend, with an exchange_code that can be used to receive an updated access_token from /connect/token

Reconfirmation of consent needed

❗️

Currently not supported

This response is not currently supported in our sandbox or production environment

If connections/extend returns action_needed: "reconfirmation_of_consent_needed", this means you have chosen not to re-confirm consent inside your application. Because consent needs to be fully informed and collected, the response will return a user_input_link that you can direct the user toward. This will direct the end-user to the auth dialog to reconfirm consent. This may then involve the user being directed to the bank for authentication. You will receive a webhook notification to the redirect_uri specified when calling /extend, with an exchange_code that can be used to receive an updated access_token from /connect/token.


Did this page help you?