vault

Revoke a handoff

kygit-handoff. Idempotent — revoking an already-terminal (claimed/expired/revoked) handoff is a no-op 200 naming its current state. Authorized at the ROUTE level by gitvault.writer, then at the SERVICE level by minter-or-owner (an active owner may revoke any handoff on the org's vaults, not only their own mints). Never lifecycle-gated.

delete/vaults/v1/{vault_id}/handoffs/{handoff_id}

Request

  • Base URL: https://api.run402.com
  • URL: https://api.run402.com/vaults/v1/{vault_id}/handoffs/{handoff_id}
  • Auth: one of:
    • HTTP bearer
    • API key in header SIGN-IN-WITH-X
    • HTTP bearer

Path parameters

vault_idstring required
handoff_idstring uuid required

Headers

SIGN-IN-WITH-Xstring required

SIWX auth header — base64-encoded JSON payload containing a signed CAIP-122 (EIP-4361) message. See https://docs.x402.org/extensions/sign-in-with-x.

Response

Revoked (or already terminal — idempotent).

handoff_idstring uuid required
state'issued' | 'adopted' | 'expired' | 'revoked' required

Changes

No recorded changes to this operation across all 1 revision of this API.