---
title: "Finish a Plaid update-mode relink and resume ingestion"
method: POST
path: "/companies/{companyId}/financial-sync/plaid/relink/{integrationId}"
tags: ["Integrations"]
---

# Finish a Plaid update-mode relink and resume ingestion

`POST /companies/{companyId}/financial-sync/plaid/relink/{integrationId}`

## Request

- Base URL: `https://api.medianfi.com/api/v1`
- URL: `https://api.medianfi.com/api/v1/companies/{companyId}/financial-sync/plaid/relink/{integrationId}`
- Auth: HTTP bearer

The client's word that Link succeeded is not trusted: Plaid is asked for the Item's own state first. An Item still reporting a reauth-class error keeps needs_reauth and answers 409. On success needs_reauth is cleared, the open reauth_required action item is resolved and an incremental sync is claimed. `status` is left untouched.

## Request body

- object
  - `state` string, required: authorizationState returned by the relink-token endpoint.
  - `redirectUri` string, uri, required

## Response `200`

Connection healed and ingestion resumed

- object
  - `success` boolean
  - `data` object
    - `integrationId` string, uuid
    - `entityId` string, uuid
    - `itemId` string, nullable
    - `needsReauth` false
    - `resolvedActionItems` integer
    - `syncJob` object, nullable: Claimed sync job, or null when none could be started.

## Other responses

- `401`: Authentication required
- `403`: Insufficient permissions or not a company member
- `404`: Integration connection not found for this company
- `409`: PLAID_RELINK_INCOMPLETE (Item still reports a reauth-class error), PLAID_RELINK_NOT_APPLICABLE (connection is not `connected`), or the authorization state belongs to a different legal entity.
- `422`: Validation error

---

[API](https://skmtc.dev/medianfi/apis/median-api.md) · [All operations](https://skmtc.dev/medianfi/apis/median-api/llms.txt) · [OpenAPI document](https://skmtc.dev/medianfi/apis/median-api/revisions/20090ea32b0d?raw)