marketplace

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

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

Authenticatie

Stuur een API-sleutel mee als bearer token. Dit eindpunt vermeldt geen specifieke toestemming in de specificatie, dus geef uw sleutel de minimale rechten die nodig zijn en controleer het antwoord in plaats van zomaar wat aan te nemen.

Dit eindpunt vereist geen organisatie-id. Uw sleutel identificeert al de organisatie waartoe deze behoort, en het antwoord is hierop afgestemd.

Probeer het

Vervang alles tussen punthaakjes door uw eigen waarden en de sleutelplaatsvervanger door een sleutel uit uw dashboard.

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> }'

Ingelogd? De API-console in je dashboard vult je echte organisatie-id en je eigen sleutel in, en voert het verzoek uit tegen de live API zodat je de daadwerkelijke respons kunt zien. Open dit eindpunt in de API-console

Details

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.

Parameters

Naam	Type	Verplicht	Wat dit is
`sale_id (path)`	`string`	Ja	—

Aanvraaglichaam

Naam	Type	Verplicht	Wat dit is
`requirements`	`object`	Ja	Answer per question key, validated against the frozen schema.

Reactie

Naam	Type	Verplicht	Wat dit is
`sale_id`	`string`	Ja	—
`state`	`string`	Ja	—
`archetype`	`MarketplaceOrderArchetype`	Ja	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`	Nee	—
`package_name`	`string`	Nee	—
`turn`	`MarketplaceOrderTurn`	Ja	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`	Ja	What the order is waiting FOR — the half that makes `turn` actionable.
`is_yours`	`boolean`	Nee	Whether the caller is the party being waited on.
`is_buyer`	`boolean`	Ja	—
`deadline`	`string`	Nee	The clock that is actually running, or null when none is.
`paused`	`boolean`	Nee	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`	Nee	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`	Nee	—
`handover_required`	`integer`	Nee	—
`outstanding`	`string[]`	Nee	Question keys the buyer still owes.
`revisions_used`	`integer`	Nee	—
`revisions_included`	`integer`	Nee	—
`delivery_due_at`	`string`	Nee	—
`currency`	`string`	Nee	—
`gross_minor`	`integer`	Nee	Integer minor units. Money is never a float.
`commission_minor`	`integer`	Nee	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`	Nee	What we owe the seller — a trade payable, not money held on trust.
`requirements_schema`	`object[]`	Nee	The questions AS ASKED, frozen at purchase. A seller who rewrites their questions tomorrow cannot change what this buyer was asked.
`requirements`	`object`	Nee	The buyer's answers, in the same `{key: {v: …}}` envelope.
`requirements_submitted_at`	`string`	Nee	—
`handover_items`	`MarketplaceHandoverItem[]`	Nee	—
`last_revision_reason`	`string`	Nee	—

Fouten die dit eindpunt kan retourneren

401 · 404 · 422

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