marketplace

POST /v1/marketplace/orders/{sale_id}/handover/{item_id}

Tick one handover item — from your side of the order.

All marketplace endpoints

Authentication

Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/marketplace/orders/{sale_id}/handover/{item_id} \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "action": <string<transferred, confirm, flag>> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

docs/83 §4.4. Each item carries **two** confirmations: the seller marks it transferred, and the buyer marks it received. Funds release only when every required item is buyer-confirmed — a seller-only tick is not delivery. Which action a caller may take is decided server-side by which side of the order they are on. A seller marking an item received on the buyer's behalf would be a seller releasing their own money. A buyer can flag a single item as missing or wrong **without rejecting the whole sale**; that flag is what opens a dispute, with the checklist and the order chat as evidence. `order_accepted` is true when this tick was the last required one and the money has been released.

Parameters

NameTypeRequiredWhat it is
sale_id (path)stringYes
item_id (path)stringYes

Request body

NameTypeRequiredWhat it is
actionstring<transferred, confirm, flag>Yes`transferred` is the seller's only action; `confirm` and `flag` are the buyer's. Enforced server-side — a seller marking an item received on the buyer's behalf would be a seller…
notestringNoThe seller's evidence, the buyer's note, or — on `flag` — the required reason.

Response

NameTypeRequiredWhat it is
itemMarketplaceHandoverItemYes
confirmedintegerYes
requiredintegerYes
order_acceptedbooleanYesTrue when this tick was the last required one and the money has been released. Reported because the buyer's last tick is the most consequential moment of the order and a screen…
statestringYes

Errors this endpoint can return

401 · 404 · 422