Request to vault a unit
Records the owner’s approval to place the unit’s item with a vault. Authorized by the owner’s tap session token. The request stays pending until the vault confirms it has the item, and expires after 30 days. Send an Idempotency-Key header to make a retry safe.
Authorizations
Use Authorization: Bearer end_sess_* for V2 browser session tokens (e.g. end_sess_ZW5kc3RhdGUtZXhhbXBsZS1zZXNzaW9uLXRva2VuAAA).
Headers
Unique key that makes this request safe to retry. Replaying the key with the same body returns the original response with Idempotent-Replayed: true; replaying it with a different body returns 409 idempotency.key_conflict.
1 - 255"a1b2c3d4-0000-4000-8000-000000000000"
Path Parameters
Body
The vault to hold the item. It must be the brand's default vault or another vault the brand allows.
The 32-byte nonce in the owner's signed approval.
^0x[0-9a-fA-F]{64}$The owner's signature over the approval.
^0x(?:[0-9a-fA-F]{2})+$Response
The pending vault request.
pending, submitted, active, unvault_waiting, unvaulting, unvaulted, cancelled, expired, rejected, failed Why the request was rejected: the vault's reason, or owner_changed when the unit changed hands after its owner approved.
wrong_item, chip_unreadable, unacceptable, owner_changed, null Whether the item is ready to ship: its waiting period has ended and nothing holds it. The vault records dispatch with a tap of the item from then on.
When the vault's tap recorded the item's dispatch. Endstate then completes the unvault; the vault hands the item over once the request reads unvaulted.
When a pending request expires; null once it has moved on.

