Refreshes with LoginId

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
}

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