Skip to main content
POST
Reauthorize a connection

Authorizations

Authorization
string
header
required

Pass your secret key in the Authorization header as a Bearer token: Authorization: Bearer sk_test_... (sandbox) or Bearer sk_live_... (production).

Keys are created in the developer portal and the plaintext secret is shown exactly once at creation. Treat them like passwords — never embed them in mobile apps or front-end code.

Path Parameters

connection_id
string
required

Canonical Connection id (con_<SOURCE>_<bankAccountId>) of the connection to repair. The placeholder UUID from initiate and any con_PDF_* id are rejected with 400.

Example:

"con_FINICITY_41294"

Body

application/json

No body. Send Content-Length: 0 so the upstream load balancer doesn't reject the request with 411.

The body is of type object | null.

Response

A hosted reauthorization URL, plus the source it leads to. A different source means the URL starts a new connection. A matching source targets repair of the existing connection, but does not guarantee stable ids if Finicity changes the login.

Result of POST /v3/connections/{connection_id}/reauthorize: the connection id (echoed for correlation), the source the hosted URL actually leads to, and a reauthorize action carrying that URL.

connection_id
string
required
Example:

"con_FINICITY_41294"

source
enum<string>
required

The source the hosted URL leads to. Usually the same source as the connection_id you passed. Repairs aim to retain existing ids, but a matching source does not guarantee this: Finicity may issue a different login that cannot be matched back to the existing connection.

When it differs, the URL hands the end-user to a different provider (today: a Finicity connection at a bank we now serve exclusively through MX). Completing it creates a new connection with a new con_ id and new acc_ / txn_ ids under the same Client; the old connection is not repaired. Compare this against the source segment of the connection_id you sent, and if it differs, re-list GET /v3/clients/{client_id}/connections and GET /v3/accounts?client_id=... after the connection.active webhook rather than expecting the old ids to come back.

Available options:
FINICITY,
MX,
FDE,
PDF
Example:

"FINICITY"

action
object
required