unsupported-conversion

422 Unprocessable Content — Both formats are individually supported, but the requested from → to pair is not a supported conversion (some formats are normalize-only, and file.

`unsupported-conversion`

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

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

Both formats are individually supported, but the requested from → to pair is not a supported conversion (some formats are normalize-only, and file targets are render-only).

Common causes

Requesting a pair outside the registry (e.g. converting between two statement dialects directly)
Using a normalize-only source (e.g. camt.110/camt.111) as a conversion source
Using a render-only file target (CSV/OFX) as a from

How to fix it

Check the convertsTo list for your source format at GET /v1/formats.

Does it bill?

Yes on a live key. 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?

unsupported-conversion