marketplace

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

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

Tabbatar da Asali

Aiko da maɓallin API a matsayin bearer token. Wannan ma'anar ba ta bayyana takamaiman izini ba a cikin ƙayyadaddun bayanai, don haka ba wa maɓallin ku mafi ƙarancin abin da yake buƙata kuma ku bincika amsar maimakon yin zato.

Wannan wurin ƙarewa ba ya buƙatar ID na ƙungiya. Maɓallin ku ya riga ya gano ƙungiyar da yake ciki, kuma an iyakance amsa a kanta.

Gwada

May gurbin komai da ke cikin kusurwa da ƙimar ka, kuma may gurbin maballi da maballi daga allon sarrafa ka.

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

An shiga? Na'urar sarrafa API da ke cikin sashin kulawarka tana cika ainihin lambar ƙungiyarka da maɓallinka naka, sannan tana gudanar da buƙatar a kan ainihin API don haka zaka iya ganin amsar gaske. Buɗe wannan tashar a cikin na'urar kula da API

Bayani

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.

Sigogi

Suna	Nau'i	Ana buƙata	Abin da yake
`sale_id (path)`	`string`	Eh	—

Jikin buƙata

Suna	Nau'i	Ana buƙata	Abin da yake
`requirements`	`object`	Eh	Answer per question key, validated against the frozen schema.

Martani

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

Kuskuren da wannan matsaya za ta iya maido wa

401 · 404 · 422

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