---
title: "Recipient pin status (owner + step-up)"
method: GET
path: "/vaults/v1/{vault_id}/recipients/{principal_id}"
tags: ["vault"]
---

# Recipient pin status (owner + step-up)

`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

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).

## Path parameters

- `vault_id` string, required
- `principal_id` string, required

## Headers

- `SIGN-IN-WITH-X` string, required

## Response `200`

The recipient_pin_status_response

- object

## Other responses

- `403`: VAULT_ACCESS_DENIED

---

[API](https://skmtc.dev/run402/apis/run402-api.md) · [All operations](https://skmtc.dev/run402/apis/run402-api/llms.txt) · [OpenAPI document](https://skmtc.dev/run402/apis/run402-api/revisions/893607557f50?raw)