connection-failed

422 Unprocessable Content — Delivery to your accounting connection could not proceed because the connection is broken — typically a revoked or expired OAuth authorization.

`connection-failed`

HTTP 422 Unprocessable Content
Content-Type: application/problem+json

{
  "type": "https://docs.transmute.403fin.io/errors/connection-failed",
  "title": "...",
  "status": 422,
  "detail": "...",
  "requestId": "req_01J..."
}

Delivery to your accounting connection could not proceed because the connection is broken — typically a revoked or expired OAuth authorization.

Common causes

The authorization was revoked on the platform side
The connected organization/tenant was removed
Expired refresh credentials

How to fix it

Re-connect the platform (Accounting Connections); the result file remains fetchable via GET /v1/jobs/{id} until the job TTL.

Does it bill?

Yes on a live key (the conversion work completed; delivery failed). See Test vs Live Keys for the full billing rules.

Errors Overview — the problem+json shape and the closed catalog
Every response carries an X-Request-Id; quote it when contacting support.

Was this page helpful?

connection-failed