Error and status code reference

Registry Stack HTTP products own their error contracts. Use the product reference that matches the service you call instead of assuming codes or response shapes carry across products.

Registry Evidence

Registry Evidence problem types is the maintained reference for the Gateway’s closed problem set. The runtime-owned generator reproduces its committed schema and OpenAPI artifacts under CI.

Evidence OID4VCI supporting service

The OID4VCI delivery service has its own protocol error vocabulary in the committed OpenAPI artifact. A request the web framework refuses before the protocol handler runs, for a malformed body, an oversize body, or an unsupported content type, is answered in the same JSON error shape as the service’s own refusals. A request over its rate budget is answered 429 with Retry-After.

Evidence OID4VP supporting service

The OpenID4VP verifier answers wallets with the OAuth error shape and no description, and answers callers with problem responses defined in its committed OpenAPI artifact. A session that failed because the wallet reported an error carries one failureCategory from a closed set; a refusal for a spent budget or a full presentation store is 503 or 429 with Retry-After.

Retired Relay codes

Registry Relay and its problem-code catalog were retired in Registry Stack 0.39.0. Existing integrations can use the immutable 0.38.0 documentation while planning a replacement. See the Relay retirement decision.