Platitun · API · The deal · Mark the delivery

Mark the delivery

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

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

The product is delivered. For a subscription and an account with a subscription the next charge date is REQUIRED: it is the proof of activation and the buyer verifies it in seconds. Without it the delivery is not accepted.

Check noteRejected: the delivery went through but the buyer never saw the note. Silently ignoring that leaves them without an explanation.

Request fields

Field	Type	What it is
`nextChargeDay`	`string`	The next charge date at the vendor, like 2026-09-20. Required for a subscription and an account with a subscription.
`note`	`string`	A note to the buyer: what they got and what to do next.

Response fields

Field	Type	What it is
`status`	`string`	The state after delivery.
`noteRejected`	`string\|null`	The delivery happened but the note did NOT pass the contact filter. Rewrite it without contacts and send it as a message.

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.
`need_next_charge`	A subscription and an account with a subscription require the next charge date: it is the proof of activation and the buyer verifies it in seconds.

Example

POST /api/v1/orders/cmt2x34ms001boz019p80jgzn/deliver
Idempotency-Key: deliver-1042-once

{ "nextChargeDay": "2026-09-20", "note": "Подписка активна, продление автоматическое." }

→ 200 { "order": "cmt2…", "status": "delivered", "noteRejected": null }

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}/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