Vault

Authoritatively retire a signed transaction artifact

Changed on

Requires an owner/admin browser session with recent MFA. Solana retirement succeeds only when the exact deterministic signature is absent from chain history and its byte-classified ordinary blockhash is expired. Durable-nonce and unclassified artifacts remain blocked. Landed artifacts are reconciled instead. Provider uncertainty and unsupported EVM artifacts remain non-terminal.

post/vault/{agentId}/transactions/{txId}/retire-signed

Request

Headers

X-Steward-Request-Timestampstring

Unix seconds, Unix milliseconds, or HTTP/ISO timestamp. Sensitive mutating routes require this or X-Steward-Request-Expires-At when request-expiry or request signatures are enforced.

X-Steward-Request-Expires-Atstring

Unix seconds, Unix milliseconds, or HTTP/ISO expiry time. Sensitive mutating routes require this or X-Steward-Request-Timestamp when request-expiry or request signatures are enforced.

X-Steward-Signaturestring

Authorization signature for sensitive mutating routes when STEWARD_REQUIRE_AUTH_SIGNATURE=true or production enforcement is enabled. Use v1=<hmac-sha256> or p256=<signature>.

X-Steward-Signing-Key-Idstring

Tenant request-signing key id used to select a managed HMAC signing key. Required when signing with a managed tenant key; omit only for static or app-client signing secrets.

Idempotency-Keystring

Required for signed sensitive requests and recommended for all sensitive mutating requests. Replays are scoped to authenticated or explicitly signed contexts.

Request body

reasonstring required

Response

JSON response

oktrue required

Changes