vault

Reclaim a stalled allocation (owner-only)

Owner-only (gitvault.create). After the reclaim window with no genesis, supersedes the stalled allocation (republished with status: "superseded") and issues a fresh one at generation + 1 with the reclaimer's own creator keys. Serialized with genesis admission on the vault row: once a generation-zero admission passed its irreversible fence, reclaim is refused.

post/vaults/v1/{vault_id}/allocations/reclaim

Request

  • Base URL: https://api.run402.com
  • URL: https://api.run402.com/vaults/v1/{vault_id}/allocations/reclaim
  • 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.

Request body

client_creation_idstring required

32 lowercase hex — MUST differ from the superseded allocation's.

creator_signing_pubkeystring required
creator_encryption_pubkeystring required

Response

Fresh allocation issued

repo_idstring
project_idstring
org_idstring uuid
allocation_generationinteger
allocationobject

The control-plane-signed allocation record, exactly as stored.

allocation_sha256string
deduplicatedboolean
next_actionsobject[]

Changes

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