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