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

# Reconnect

> Bring an end user back into Flinks Connect to answer MFA — whether their session was just interrupted or an existing connection needs a live refresh.

Reconnect lets an end user re-enter Flinks Connect to answer MFA and keep their bank connection alive — whether their original session was just interrupted, or it completed days ago and now needs a live refresh.

## When to use it

Two scenarios, one feature:

* **Interrupted session** — the end user closed the tab or navigated away mid-MFA. Bring them back to where they left off.
* **Refresh an existing connection** — a previously authorized account needs fresh data, and the financial institution requires MFA again (e.g., Nightly Refresh failed, on-demand transaction update, MFA answers changed at the bank).

In both cases the outcome is the same: the end user answers MFA in Flinks Connect, and the connection moves forward.

## How it works

Pick the entry point that matches your starting state.

### Interrupted session — you have a live `requestId`

Reload Flinks Connect with the existing `requestId`. The end user lands directly on the MFA prompt — no restart.

```
https://{instance}-iframe.private.fin.ag/?requestId={requestId}&...
```

An HTTP `203` from a session API call means MFA is pending and the session is resumable.

| Token           | Validity                |
| :-------------- | :---------------------- |
| `requestId`     | 8 minutes of inactivity |
| Authorize token | 15 minutes              |

If the `requestId` has expired, the end user will need to start a new session.

### Refresh — you have a stored `loginId`

Call [/Authorize](/api/authorize/endpoints/authorize) with:

* `LoginId` — the customer's existing `loginId`
* `MostRecentCached: false` — force a live connection to the financial institution
* `Save: true` — persist the refreshed data

If the financial institution requires MFA, the API returns a `203` with security challenges. Open Flinks Connect with the same `requestId` and have the end user answer the MFA there:

```
https://{instance}-iframe.private.fin.ag/?requestId={requestId}&...
```

Once authorized, call [/GetAccountsDetail](/api/connect/endpoints/account-linking/get-accounts-detail) with the `requestId` to retrieve fresh data.

## Preserve previously selected accounts

If the original session used the [Account Selector](/guides/connect/flinks-connect/widget#account-selection), pass the previously selected account IDs into the Reconnect iframe with [`resumeSelectedAccounts`](/guides/connect/flinks-connect/widget#preserve-account-selection-across-reconnect-sessions). Flinks Connect skips the selector, applies the filter on the backend, and surfaces the IDs in the `REDIRECT` event and redirect URL — so [/GetAccountsDetail](/api/connect/endpoints/account-linking/get-accounts-detail) returns only the originally selected accounts.

```
https://{instance}-iframe.private.fin.ag/?requestId={requestId}&resumeSelectedAccounts={id1},{id2}
```

## Common use cases

* Refreshing data when Nightly Refresh has failed for an account
* Collecting updated transaction history on demand
* Re-authorizing when an account's MFA answers have changed at the bank