Platitun · API · The deal · Read the buyer’s vault

Read the buyer’s vault

POST /api/v1/orders/{id}/handover/reveal

Key scope: orders · changes data, the Idempotency-Key header is required

The buyer also uses a vault — for instance for the email a subscription should be issued to. Someone else’s vault can be read EXACTLY ONCE: a repeat honestly answers “already opened”. Your own vault cannot be read at all.

Once read, keep it. There is no second time, and the marketplace cannot repeat it: it does not know the content.

Request fields

Field	Type	What it is
`handover` required	`string`	The vault id from the order vault list.

Response fields

Field	Type	What it is
`secret`	`string`	The content — for the first and last time.

Refusal reasons

A rule refusal arrives as {"error":"rejected","refusal":{"kind":"…"}} with status 409. Refusals common to all endpoints are in the rules section.

Code	What happened and what to do
`not_found`	The record does not exist or is not yours. The ownership condition is in the database query itself, so someone else’s record looks like a missing one.
`vault_empty`	The vault was already opened or is empty. Someone else’s vault can be read exactly once, and a repeat says so honestly.
`vault_off`	The marketplace vault is not configured, so there is nowhere to keep secrets. That is our problem, not yours: contact support.

Nearby in this section

GET /api/v1/orders — My orders
GET /api/v1/orders/{id} — One order
POST /api/v1/orders/{id}/confirm — Take the order
POST /api/v1/orders/{id}/decline — Decline the order
POST /api/v1/orders/{id}/deliver — Mark the delivery
POST /api/v1/orders/{id}/messages — Message the buyer
GET /api/v1/orders/{id}/handover — The order vaults
POST /api/v1/orders/{id}/handover — Put credentials into a vault
POST /api/v1/orders/{id}/dispute/reply — Answer a dispute
GET /api/v1/reviews — Reviews about me
POST /api/v1/reviews/{id}/reply — Reply to a review
GET /api/v1/complaints — My complaints
POST /api/v1/complaints — Complain about a buyer
GET /api/v1/work-mode — Work mode and presence
PUT /api/v1/work-mode — Set the work mode