Ironfang Finance API problem type

`billing_moved`

Billing moved. HTTP 410.

What it means

Plans and subscriptions for Ironfang Finance alone are retired. Usage, limits, payment and invoices belong to the billing account, one per organisation for every Ironfang product.

What to do

Read the account's usage and billing at /billing/v1, and Finance's own usage at GET /v1/einvoices/usage.

What the response carries

type: https://ironfang.com/problems/billing_moved, this page.
status: Always 410 for this code.
code: billing_moved. 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.