Platitun · API · The deal · One order

One order

GET /api/v1/orders/{id}

Key scope: orders · read only

The whole order: state, deadlines, the product snapshot at purchase time, the chat and the vaults. The snapshot exists so a dispute a month later is judged by what the buyer saw, not by the current listing.

Response fields

Field	Type	What it is
`status`	`string`	The order state.
`snapshot`	`object`	The product snapshot: name, plan, delivery time, guarantee.
`messages`	`array`	The chat: who, when, what. The last two hundred messages.
`handovers`	`array`	The order vaults: whose and whether opened. No secrets here.

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.

Nearby in this section

GET /api/v1/orders — My orders
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}/handover/reveal — Read the buyer’s 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