marketplace
GET /v1/marketplace/orders/{sale_id}/dispute
The dispute on an order, and whether the buyer may raise one.
Authentication
Send an API key as a bearer token. This endpoint checks no specific permission, so any key for your organisation can call it.
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 GET https://api.zinndigital.com/v1/marketplace/orders/{sale_id}/dispute \
-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
W43-74 (D25235). Either party reads it — the seller must see the buyer's reason to answer it in the order chat. can_raise uses the same rule the POST enforces: an order is disputable once delivered, while a revision is requested, once its delivery date has passed, or when an asset-transfer handover item is flagged. Staff identities are never included.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
sale_id (path) | string | Yes | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
sale_id | string | Yes | — |
state | string | Yes | — |
is_buyer | boolean | Yes | — |
can_raise | boolean | Yes | — |
refusal_code | object | Yes | — |
dispute | object | Yes | — |
Errors this endpoint can return
401 · 404