Anatomy of an error (RFC 9457)
Errors are returned with Content-Type: application/problem+json and exactly these
fields:
{
"type": "https://api.orbitum.io/problems/CEX_NO_STOCK",
"title": "Insufficient ORBIS stock to reserve",
"status": 400,
"code": "CEX_NO_STOCK",
"detail": "No ORBIS available on the CEX stock Safe",
"instance": "/api/v1/cex/orders",
"requestId": "req_8f3c1a"
}
| Field | Use |
|---|---|
code | Stable machine identifier — branch on this. |
type | Problem-type URI: https://api.orbitum.io/problems/{code}. |
title / detail | Human text — for logs only; may change; never render verbatim. |
status | HTTP status. |
instance | The request path. |
requestId | Correlation id (also the X-Request-Id header). |
There is no errors[] array.