marketplace

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

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

Xaqiijinta aqoonsiga

U dir fure API ahaan calaamad muujisa (bearer token). Barta dhammaadka ee kani ma caysino luqad ahaan oggolaansho gaar ah oo ku dhex jirta qeexidda, markaa sii furahaaga inta ugu yar ee uu u baahan yahay oo fiiri jawaabta halka aad wax ka qaadan lahayd.

Boggan ma qaato aqoonsiga ururka. Furahaagu wuxuu horay u aqoonsanayaa ururka uu ka tirsan yahay, jawaabtuna waxay ku kooban tahay halkaas.

Isku day

Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.

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

Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API

Faahfaahin

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.

Cabiraha

Magaca	Nooc	Loo baahan yahay	Maxay tahay
`sale_id (path)`	`string`	Haa	—

Codsiga jidhkiisa

Magaca	Nooc	Loo baahan yahay	Maxay tahay
`requirements`	`object`	Haa	Answer per question key, validated against the frozen schema.

Jawaab

Magaca	Nooc	Loo baahan yahay	Maxay tahay
`sale_id`	`string`	Haa	—
`state`	`string`	Haa	—
`archetype`	`MarketplaceOrderArchetype`	Haa	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 appl…
`listing_title`	`string`	Maya	—
`package_name`	`string`	Maya	—
`turn`	`MarketplaceOrderTurn`	Haa	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…
`waiting_on`	`MarketplaceOrderWaitingOn`	Haa	What the order is waiting FOR — the half that makes `turn` actionable.
`is_yours`	`boolean`	Maya	Whether the caller is the party being waited on.
`is_buyer`	`boolean`	Haa	—
`deadline`	`string`	Maya	The clock that is actually running, or null when none is.
`paused`	`boolean`	Maya	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`	Maya	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`	Maya	—
`handover_required`	`integer`	Maya	—
`outstanding`	`string[]`	Maya	Question keys the buyer still owes.
`revisions_used`	`integer`	Maya	—
`revisions_included`	`integer`	Maya	—
`delivery_due_at`	`string`	Maya	—
`currency`	`string`	Maya	—
`gross_minor`	`integer`	Maya	Integer minor units. Money is never a float.
`commission_minor`	`integer`	Maya	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 mark…
`vendor_net_minor`	`integer`	Maya	What we owe the seller — a trade payable, not money held on trust.
`requirements_schema`	`object[]`	Maya	The questions AS ASKED, frozen at purchase. A seller who rewrites their questions tomorrow cannot change what this buyer was asked.
`requirements`	`object`	Maya	The buyer's answers, in the same `{key: {v: …}}` envelope.
`requirements_submitted_at`	`string`	Maya	—
`handover_items`	`MarketplaceHandoverItem[]`	Maya	—
`last_revision_reason`	`string`	Maya	—

Cilladaha ay bartaani soo celin karto

401 · 404 · 422

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