vault

Retire a previous owner's vault writers after a project transfer (owner + step-up)

Owner + step-up (gitvault.rotate). Gateway-blocks every active writer key whose principal holds no active developer-or-above membership on the vault's current organization, and records reason: "org_transferred" on the audit trail. Ordinary pushes then refuse EPOCH_ROTATION_REQUIRED until a rotate_epoch with reason writer_key_revoked removes exactly that set; run402 repos access retire-previous-owner calls this route and commits that rotation. A project transfer never does this on its own. Retiring protects only what is written after the rotation: anyone who held the vault's key before keeps what they could already read. Idempotent; reports retired: [] when nothing is outside the organization.

post/vaults/v1/{vault_id}/writers/retire-previous-owner

Request

  • Base URL: https://api.run402.com
  • URL: https://api.run402.com/vaults/v1/{vault_id}/writers/retire-previous-owner
  • 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).

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 retired set

repo_idstring
rotation_requiredboolean
notestring
next_actionsobject[]

Changes

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