Ironfang Finance API problem type

`unsupported_content_type`

Unsupported content type. HTTP 415.

What it means

The body is not in a media type the operation accepts: XML (or multipart form data) for validation, uncompressed JSON for generation and jobs, a ZIP for report verification. Archives and compressed bodies are refused where a document is expected.

What to do

Send the content itself in the media type the operation documents.

What the response carries

type: https://ironfang.uk/problems/unsupported_content_type, this page.
status: Always 415 for this code.
code: unsupported_content_type. Stable: branch on this, not on the wording of title or detail.
detail: What happened this time, safe to show to a person. It never carries invoice content.
request_id: The same value as the X-Ironfang-Request-ID header. Quote it to support.
retry_after_seconds: Never present for this code.
outcome: Absent. This code is not a statement about any document.

Problems follow RFC 9457 and are served as application/problem+json. A validation finding is never a Problem: an invalid invoice is a successful response that lists its findings. See every problem type, the Finance guide and the OpenAPI contract.