Refreshes with LoginId

Modified on Tue, 16 Nov, 2021 at 12:51 PM

In order to update the end-user's data and therefore, fetch current balance and most recent transactions, a refresh (a.k.a. live) call is required. Or, if your Authorize call is getting stuck with an error message and you'd like to try refreshing before reengaging the user, this can be done via API in a similar way to the usual caches calls already explained in other articles.


The only difference sits on the Authorize call. In refreshes, the parameter "MostRecentCached" must be set to false, so Flinks can know that it's time to reconnect to that user's FI! As good practice, please make sure to add the "Save" parameter as well.


Below you will find how this looks like:


1) Authorize (live mode)


Body parameters:

{
"LoginId":"{{LoginId}}",
"MostRecentCached": false,
"Save": true
}


If a 200 is returned, time to proceed to the aggregation endpoint of your choice. However, if any credential or MFA related errors occur, the alternative is to reengage the user and as them to reconnect through Flinks Connect.


As an example, let's follow with the flow by using GetAccountsDetail.


2) GetAccountsDetail


Body parameters:

{
    "RequestId":"{{RequestId}}"
}


In case a 200 is returned, the flow is done! However, in case you get back a 202 OPERATION PENDING error, you must engage on the Asynchronous Flow, as described on this article.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article