marketplace

POST `/v1/marketplace/orders/{sale_id}/requirements`

The buyer's brief — and the thing that starts the delivery clock.

Упълномощаване

Изпратете API ключ като носител (bearer token). Тази точка за достъп не указва конкретно разрешение в спецификацията, затова дайте на ключа си най-малкото необходимо и проверете отговора, вместо да правите предположения.

Този ендпойнт не изисква идентификатор на организация. Вашият ключ вече идентифицира организацията, към която принадлежи, и отговорът е ограничен до нея.

Опитайте

Заменете всичко в квадратни скоби със собствени стойности, а ключовия заместващ символ – с ключ от вашето табло за управление.

curl -X POST https://api.zinndigital.com/v1/marketplace/orders/{sale_id}/requirements \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "requirements": <object> }'

Влязохте ли в профила си? API конзолата във вашето табло за управление попълва действителното идентификационно число на вашата организация и вашия собствен ключ и изпълнява заявката спрямо реалното API, за да можете да видите действителния отговор. Отворете този крайpoint в API конзолата

Детайли

docs/147 §2. A paid order used to arrive carrying a package name and nothing else: the seller could not start, the clock was running, and there was no channel to ask. Submitting is what starts the delivery clock. Until this call the seller's deadline does not exist, so the days a buyer spends writing their brief are never billed against the seller's deadline and a seller is never late for work they could not begin. The questions come from the order's own frozen requirements_schema — a snapshot taken at purchase, so a seller who rewrites their questions tomorrow cannot change what this buyer was asked. Buyer only. A seller gets a 404, the same way acceptance is the buyer's act alone.

Параметри

Име	Тип	Задължително	Какво представлява
`sale_id (path)`	`string`	Да	—

Тяло на заявката

Име	Тип	Задължително	Какво представлява
`requirements`	`object`	Да	Answer per question key, validated against the frozen schema.

Отговор

Име	Тип	Задължително	Какво представлява
`sale_id`	`string`	Да	—
`state`	`string`	Да	—
`archetype`	`MarketplaceOrderArchetype`	Да	How this order behaves. Adding a CATEGORY is configuration; adding an ARCHETYPE is a build. Every order-side decision — whether a delivery clock exists, whether auto-accept…
`listing_title`	`string`	Не	—
`package_name`	`string`	Не	—
`turn`	`MarketplaceOrderTurn`	Да	Whose move it is. `staff` is a real answer, not a fallback: a disputed order is genuinely waiting on us, and telling a buyer "waiting for the seller" while a moderator holds it is…
`waiting_on`	`MarketplaceOrderWaitingOn`	Да	What the order is waiting FOR — the half that makes `turn` actionable.
`is_yours`	`boolean`	Не	Whether the caller is the party being waited on.
`is_buyer`	`boolean`	Да	—
`deadline`	`string`	Не	The clock that is actually running, or null when none is.
`paused`	`boolean`	Не	A clock EXISTS but is stopped — the revision pause. Distinct from a null deadline, which also covers an order that never had a clock at all.
`overdue`	`boolean`	Не	Never true while `delivery_due_at` is null: null means the clock has not started, which is exactly the state of an order whose buyer has not written their brief yet.
`handover_confirmed`	`integer`	Не	—
`handover_required`	`integer`	Не	—
`outstanding`	`string[]`	Не	Question keys the buyer still owes.
`revisions_used`	`integer`	Не	—
`revisions_included`	`integer`	Не	—
`delivery_due_at`	`string`	Не	—
`currency`	`string`	Не	—
`gross_minor`	`integer`	Не	Integer minor units. Money is never a float.
`commission_minor`	`integer`	Не	The platform's commission, as its own figure. Present for the SELLER and null for the buyer — to a buyer the price is the price. The platform is merchant of record on every…
`vendor_net_minor`	`integer`	Не	What we owe the seller — a trade payable, not money held on trust.
`requirements_schema`	`object[]`	Не	The questions AS ASKED, frozen at purchase. A seller who rewrites their questions tomorrow cannot change what this buyer was asked.
`requirements`	`object`	Не	The buyer's answers, in the same `{key: {v: …}}` envelope.
`requirements_submitted_at`	`string`	Не	—
`handover_items`	`MarketplaceHandoverItem[]`	Не	—
`last_revision_reason`	`string`	Не	—

Грешки, които този крайpoint може да върне

401 · 404 · 422

POST /v1/marketplace/orders/{sale_id}/requirements