vault

Recipient pin status (owner + step-up)

Owner + step-up (gitvault.rotate, protocol rev 43 D206). Returns this principal's pin_status ("pinned"|"unpinned") + pinned_fingerprint, current_base_pin_manifest_sha256/current_recipient_state_version (the values a FRESH /confirm or /repin call would bind right now), and up to 20 outstanding (unconsumed) recipient_confirmation_receipts in (issued_at DESC, object_id DESC) order, each classified "applicable" (an admission citing it would succeed right now) or "superseded" (stale — a fresh /confirm or /repin call is safe to make freely).

get/vaults/v1/{vault_id}/recipients/{principal_id}

Request

  • Base URL: https://api.run402.com
  • URL: https://api.run402.com/vaults/v1/{vault_id}/recipients/{principal_id}
  • 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 pin status is being read.

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 recipient_pin_status_response

object required

Changes

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