POST /v1/marketplace/orders/{sale_id}/zinn-asset

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}/zinn-asset \
  -H "Authorization: Bearer zdk_live_…"

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/714 §3. The move runs by itself when the sale is created; this runs it again once whatever it named has been fixed. Either party may call it; it only ever moves the asset towards the buyer. A refusal is a 200 with outcome: refused and the reason — the reason is also written onto the order's checklist row, and an error status would roll that record back.

Parameters

Response

Errors this endpoint can return

401 · 404 · 409