Reconnect a bank connection

POST 
/api/v1/bank_connections/:id/reconnect

Issues a NEW consent session for a connection that already exists, typically after expired or error. The connection's own status does NOT change on this call - a new session is an intention, not evidence, so status still advances only on a webhook or a sync. A human must open consent_url in a browser, exactly as on the first connection. No user_email is taken here: the provider's manage-an-existing-item flow identifies the item, not a person.

Request

Responses

200

A new consent session was opened. consent_url carries the page the user must visit; the connection's status is unchanged.

422

The request was refused, and code says which of four. validation_failed - the Idempotency-Key header is missing, or outside the accepted 1-255 characters; details.idempotency_key says which, and nothing was performed because the key check runs in front of the action. invalid_argument - redirect_url is not one of the URIs registered for your application, or this connection has no provider-side item to reconnect; details names which. provider_quota_exceeded - the aggregator will not open one more session for this account, so free a slot or move to another plan, because retrying unchanged is refused again. operation_failed - the aggregator refused the session for a transient reason, so retry.