Error Cataloginvalid-input

invalid-input

400 Bad Request — The request itself could not be processed: a malformed JSON envelope, a missing to or message, an unknown option value, a bad query parameter, an .

invalid-input

HTTP 400 Bad Request
Content-Type: application/problem+json

{
  "type": "https://docs.transmute.403fin.io/errors/invalid-input",
  "title": "...",
  "status": 400,
  "detail": "...",
  "requestId": "req_01J..."
}

The request itself could not be processed: a malformed JSON envelope, a missing to or message, an unknown option value, a bad query parameter, an incompatible Accept header, an unrecognized Content-Type, a reserved validation level, or a source message that would not parse at all on convert/normalize.

Common causes

  • The MT/XML body is structurally broken (unbalanced block braces, truncated document)
  • You sent a Content-Type outside the three accepted forms (JSON envelope, text/plain/application/x-swift-mt, application/xml)
  • The JSON envelope is missing to or message, or an option has a value outside its enum
  • An Idempotency-Key header outside 1–255 characters

How to fix it

Check errors[] in the response body — field-level entries name the offending field. For unparseable messages, run the same body through POST /v1/validate?level=syntax with a test key to get structured findings.

Does it bill?

Yes on a live key — the engine parsed your input in order to reject it. See Test vs Live Keys for the full billing rules.

Was this page helpful?