marketplace

GET /v1/marketplace/orders/{sale_id}

The order workspace — one order, from your side of it.

Ҳамаи нуқтаҳои ниҳоии marketplace

Санҷиши ҳаққоният

Kalitи API-ро ҳамчун token-и bearer фиристед. Ин нуқтаи ниҳоӣ дар мушаххасот иҷозати мушаххасеро нишон намедиҳад, бинобар ин ба калиди худ ҳадди ақали заруриро диҳед ва ба ҷои тахмин кардан, ҷавобро санҷед.

Ин нуқтаи поёнӣ ягон рақами мушаххаси созмонро талаб намекунад. Калиди шумо аллакай созмонеро, ки ба он тааллуқ дорад, муайян мекунад ва ҷавоб ба он маҳдуд карда мешавад.

Санҷидан

Ҳар чизро дар қаavски кунҷӣ бо қиматҳои худ ва ҷойи нигоҳдорандаи калидро бо калима аз панели идоракунии худ иваз кунед.

curl -X GET https://api.zinndigital.com/v1/marketplace/orders/{sale_id} \
  -H "Authorization: Bearer zdk_live_…"

Воarid шудаед? Консоли API дар панели идоракунии шумо рақами мушаххаси ташкилоти воқеӣ ва калиди худро пур мекунад ва дархостро бар зидди API-и фаъол иҷро мекунад, то шумо посухи воқеиро бубинед. Ин нуқтаи ниҳоиро дар консоли API кушоед

Тафсилот

docs/147 §3. The screen where the work actually happens, for whichever party is asking. Before this there was a buyer's list and a seller's money screen, and nowhere the work happened. The payload leads with `turn` and `waiting_on` because the screen does. The anti-jumble device is one question at the top — **whose turn is it, and what is it waiting for** — and it is computed in the engine so every client answers it identically rather than each deriving it from six columns. `paused` is the revision clock, made visible. Requesting a revision pauses the acceptance window by clearing its deadline, which is correct and completely unrenderable: a null deadline looks identical to a sale that never had one. The commission split is present for the SELLER and null for the buyer. To a buyer the price is the price.

Параметрҳо

НомНамудТалаб карда мешавадИн чӣ аст
sale_id (path)stringБале

Ҷавоб

НомНамудТалаб карда мешавадИн чӣ аст
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