marketplace
POST /v1/marketplace/orders/{sale_id}/requirements
The buyer's brief — and the thing that starts the delivery clock.
認証
ベアラー トークンとして API キーを送信します。このエンドポイントでは仕様に特定の権限が記載されていないため、キーに必要な最小限の権限を付与し、推測するのではなくレスポンスを確認してください。
このエンドポイントは組織IDを受け付けません。お使いのキーによって所属する組織がすでに特定されており、レスポンスはその組織にスコープされます。
試してみる
アングルブラケット内のすべてをご自身の値に置き換え、キーのプレースホルダーをご利用中のダッシュボードのキーに置き換えてください。
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に対してリクエストが実行されるため、実際のレスポンスを確認することができます。 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 | はい | — |
リクエスト本文
| 名前 | タイプ | 必須 | これがその内容です |
|---|---|---|---|
requirements | object | はい | Answer per question key, validated against the frozen schema. |
返信
| 名前 | タイプ | 必須 | これがその内容です |
|---|---|---|---|
sale_id | string | はい | — |
state | string | はい | — |
archetype | MarketplaceOrderArchetype | はい | 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 | いいえ | — |
package_name | string | いいえ | — |
turn | MarketplaceOrderTurn | はい | 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 | はい | What the order is waiting FOR — the half that makes `turn` actionable. |
is_yours | boolean | いいえ | Whether the caller is the party being waited on. |
is_buyer | boolean | はい | — |
deadline | string | いいえ | The clock that is actually running, or null when none is. |
paused | boolean | いいえ | 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 | いいえ | 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 | いいえ | — |
handover_required | integer | いいえ | — |
outstanding | string[] | いいえ | Question keys the buyer still owes. |
revisions_used | integer | いいえ | — |
revisions_included | integer | いいえ | — |
delivery_due_at | string | いいえ | — |
currency | string | いいえ | — |
gross_minor | integer | いいえ | Integer minor units. Money is never a float. |
commission_minor | integer | いいえ | 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 | いいえ | What we owe the seller — a trade payable, not money held on trust. |
requirements_schema | object[] | いいえ | The questions AS ASKED, frozen at purchase. A seller who rewrites their questions tomorrow cannot change what this buyer was asked. |
requirements | object | いいえ | The buyer's answers, in the same `{key: {v: …}}` envelope. |
requirements_submitted_at | string | いいえ | — |
handover_items | MarketplaceHandoverItem[] | いいえ | — |
last_revision_reason | string | いいえ | — |
このエンドポイントが返すエラー
401 · 404 · 422