Platitun · API · The deal · Take the order

Take the order

POST /api/v1/orders/{id}/confirm

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

The seller’s confirmation: I take it. There are 90 seconds from the order — after that the hold expires on its own and the buyer is told you did not answer. A quick confirmation is the cheapest thing you can do for your rating.

The state_moved refusal means the order has already moved on: the buyer cancelled, the deadline passed, or you confirmed it another way. This is not your program’s bug — re-read the order.

Response fields

Field	Type	What it is
`order`	`string`	The order id.
`status`	`string`	The state after confirmation.

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.
`state_moved`	The order has already moved on: the buyer cancelled, the deadline passed, or the action was done another way. Re-read the order before retrying.

Nearby in this section

GET /api/v1/orders — My orders
GET /api/v1/orders/{id} — One 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