Complete reauthentication

Tells MagicDoor the property manager has finished signing in again in the provider's widget. MagicDoor re-checks with the provider and, if the bank is happy, puts the connection back to Active. Requires the reconciliations:write permission.

POST

https://services.magicdoor.com/accounting/company-portal/bank-feeds/connections/{connectionId}/reauthentication/complete

Authorization

Authorizationstringrequired

Bearer token — Send your API token in the Authorization header as Bearer <token>. Requests without a valid token are rejected with 401 Unauthorized.

Path parameters

connectionIdstringrequired

Snowflake id of the bank feed connection.

example: 1830472847398408100

Response

200 · The connection's status after the check.

bankFeedConnectionIdstring

The connection that was checked.

statusstring

The connection's status after the check — Active when the bank accepted the new sign-in. The value is written exactly as it appears here, in PascalCase — these particular status fields are plain strings rather than the camelCase enums used elsewhere in the API.

ActiveRequiresReauthDisconnected

401 · The access token is missing, expired, or not for this company.

403 · The caller does not hold the `reconciliations:write` permission.

404 · No bank feed connection with this id belongs to the caller's company.

422 · Either the provider still reports the connection as needing a sign-in — the problem detail carries `errorCode: "bank_feed_reauthentication_verification_failed"` — or the connection was not waiting for one, carrying `errorCode: "bank_feed_reauthentication_not_required"`.