Skip to main content
The response body is a structured error object with the following shape:
Field definitions
  • code: A unique, stable identifier for the error. It is a four-digit numeric string drawn from the shared platform error registry (for example, 0347).
  • title: A brief summary of the issue.
  • message: Detailed guidance for resolving the error.
Field-level validation Struct-level field validation failures return code 0009 with the title Validation Error and a message that names the specific field and constraint — for example, transactionType must be one of [CARD WIRE PIX CRYPTO]. Examples:
Authentication failures do not use a numeric registry code. A missing or invalid API key returns HTTP 401 with "code": "Unauthenticated", "title": "Unauthorized", and "message": "API Key missing or invalid". Match on the literal Unauthenticated string. A Bearer token that parses but lacks the required sub claim returns HTTP 401 with "code": "0474".

General errors


These errors can be returned by any Tracer API endpoint. Code 0009 also appears with the title Validation Error when field-level validation rejects a request — see the note above.

Date and time errors


Pagination errors


CEL expression errors


Rules are written as CEL (Common Expression Language) expressions. These errors are raised when a rule expression is created, updated, or evaluated.

Rule errors


Limit errors


Audit event errors


Validation request errors


These errors are returned by the transaction-validation endpoints (POST /validations and the validation queries).

Reservation errors


These errors are returned by the usage-reservation endpoints (/reservations), the two-phase reserve / confirm / release surface. Reservation requests can also return the general and validation-request errors listed above.

Multi-tenant and authentication errors


The instance returns HTTP 503 with a Retry-After header when it reaches its per-pod tenant worker cap; clients should back off and retry. A Bearer token that parses but lacks the required sub claim is rejected with HTTP 401.

Multi-tenant bootstrap errors


These codes surface only at service startup, when MULTI_TENANT_ENABLED=true and a required configuration is missing or incompatible. They appear in startup logs and prevent the service from starting; they never reach /v1/* API consumers.

Readiness probe errors


These codes are surfaced by the operational /readyz endpoint and by the worker-supervisor lifecycle. They appear in the error field of the /readyz JSON response — which carries the code only — not in /v1/* API responses. The title and message below describe each code for operator reference.