marketplace

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

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

ټول marketplace پای ټکي

تصدیق‌هویت

د بیارر ټوکن په توګه یو API کي وسپارئ. دا پای ټکی په مشخصاتو کې کوم ځانګړی اجازه لیک نه بیانوي، نو خپل کیلي ته لږترلږه هغه څه ورکړئ چې ورته اړتیا لري او د فرض کولو پر ځای ځواب وپلټئ.

دا پای نقطه د سازمان هېڅ آی ډي نه اخلي. ستاسو کیلي مخکې تر مخکې هغه سازمان په ګوته کوي چې پورې اړه لري، او ځواب ورته محدود دی.

هڅه وکړئ

د انګلیسي په زاوي پنسونو کې هرڅه د خپلو ارزښتونو سره بدل کړئ، او د کلي ځای لرونکی ستاسو د ډشبورډ د کلي سره.

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 کنسول ستاسو د اصلي سازمان ID او ستاسو خپله کیلي ډکوي، او غوښتنه د ژوندی API په وړاندې پرمخ وړي ترڅو تاسو وکولی شئ اصلي ځواب وګورئ. دا پای ټکی (endpoint) د 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هو

د غوښتنې بدن

نومډولاړیندا څه شی دی
requirementsobjectهوAnswer per question key, validated against the frozen schema.

ځواب

نومډولاړیندا څه شی دی
sale_idstringهو
statestringهو
archetypeMarketplaceOrderArchetypeهو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_titlestringنه
package_namestringنه
turnMarketplaceOrderTurnهو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_onMarketplaceOrderWaitingOnهوWhat the order is waiting FOR — the half that makes `turn` actionable.
is_yoursbooleanنهWhether the caller is the party being waited on.
is_buyerbooleanهو
deadlinestringنهThe clock that is actually running, or null when none is.
pausedbooleanنه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.
overduebooleanنه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_confirmedintegerنه
handover_requiredintegerنه
outstandingstring[]نهQuestion keys the buyer still owes.
revisions_usedintegerنه
revisions_includedintegerنه
delivery_due_atstringنه
currencystringنه
gross_minorintegerنهInteger minor units. Money is never a float.
commission_minorintegerنه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_minorintegerنهWhat we owe the seller — a trade payable, not money held on trust.
requirements_schemaobject[]نهThe questions AS ASKED, frozen at purchase. A seller who rewrites their questions tomorrow cannot change what this buyer was asked.
requirementsobjectنهThe buyer's answers, in the same `{key: {v: …}}` envelope.
requirements_submitted_atstringنه
handover_itemsMarketplaceHandoverItem[]نه
last_revision_reasonstringنه

تېروتنې چې دا پای ټکی یې بیرته راګرځولی شي

401 · 404 · 422