0Bit public documentation

Errors

Gate error responses and safe client handling.

Gate returns JSON errors. Nest validation and authorization failures use this core shape:

{
  "statusCode": 400,
  "message": "amount must be a positive decimal string",
  "error": "Bad Request"
}

Some domain errors also include a stable code and request_id. Treat unknown fields as additive and show users a neutral message unless the error is explicitly safe to expose.

Status	Meaning	Client action
`400`	Invalid body, query, state, or rail request	Fix the request; do not retry unchanged
`401`	Missing, malformed, expired, or wrong-mode credential	Replace or refresh the credential
`403`	Credential is valid but lacks entitlement, scope, role, origin, or resource access	Correct authorization; do not retry unchanged
`404`	Resource is absent or outside the partner scope	Treat as unavailable to this partner
`409`	State transition or idempotency conflict	Retrieve the existing resource before deciding whether to retry
`429`	Route limit exceeded	Wait, then retry with jitter
`500`	Unexpected Gate failure	Retry only safe reads or an idempotent write
`503`	Required Gate capability is not configured or temporarily unavailable	Pause the flow and retry later

Use the X-Request-Id response header when contacting support. Never branch on human-readable message text.