Platitun · API · The deal · Complain about a buyer

Complain about a buyer

POST /api/v1/complaints

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

A topic is required and comes from the classifier: a “just bad” complaint cannot be judged, while an accumulation of similar violations is counted automatically.

Request fields

Field	Type	What it is
`topic` required	`string`	A topic from the classifier.
`text` required	`string`	What happened.
`orderId`	`string`	The order, if the complaint is about one. It determines whom the complaint is against.
`reviewId`	`string`	The review, if the complaint is about a review.

Response fields

Field	Type	What it is
`ok`	`boolean`	The complaint is accepted.

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
`need_topic`	A topic from the classifier is required: a “just bad” complaint cannot be judged.
`too_short`	The text is too short. A one-word answer helps neither the buyer nor the review.
`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
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}/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
GET /api/v1/work-mode — Work mode and presence
PUT /api/v1/work-mode — Set the work mode