marketplace

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

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

כל נקודות הקצה מסוג marketplace

אימות

שלח מפתח API כטוקן Bearer. נקודת קצה זו אינה מציינת הרשאת ספציפית במפרט, לכן הקצה למפתח שלך את המינימום הנדרש ובדוק את התגובה במקום להניח הנחות.

נקודת קצה זו אינה דורשת מזהה ארגון. המפתח שלך כבר מזהה את הארגון שאליו הוא שייך, והתגובה מוגבלת אליו בלבד.

נסה זאת

החלף כל דבר בסוגריים זוויתיים בערכים משלך, ואת מציין מיקום המפתח במפתח מלוח הבקרה שלך.

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 הפיזי כך שתוכל לראות את התגובה בפועל. פתח נקודת קצה זו במסוף ה-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