marketplace

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

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

جميع نقاط نهاية marketplace

المصادقة

أرسل مفتاح واجهة برمجة التطبيقات (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

التفاصيل

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