vault

Declare a recipient key revoked (owner + step-up)

Owner + step-up (gitvault.rotate, protocol rev 42 D199). Declares reason:"recipient_key_revoked" admissible on this vault's ORGANIZATION — advances the same org-level watermark a member removal advances (internal.vault_recipient_state_counters), so a subsequent urgent rotate_epoch admission is not refused EPOCH_ROTATION_REQUIRED.

post/vaults/v1/{vault_id}/recipients/{principal_id}/key-revocation

Request

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

Path parameters

vault_idstring required

The vault id (src_<32 hex>); the wire field is repo_id (protocol D185).

principal_idstring required

The recipient principal whose key is being declared revoked.

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

The org's recipient-state counters after the declaration

recipient_state_versionstring
recipient_revocation_versionstring

Changes

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