marketplace
GET /v1/marketplace/conversations/{conversation_id}/messages
One thread's messages, for whichever side of it you are on.
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.
Where your organisation id goes
This endpoint takes org_id as a query parameter. Leave it out and the call covers your whole tenancy subtree; send it to narrow the call to one organisation.
Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.
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/conversations/{conversation_id}/messages \
-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/147 §5. The door both parties share — above all the SELLER's way to read a pre-sales question, which the buyer-keyed enquiry route cannot serve. Reading clears your side's unread count. Held messages are hidden from both parties.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
conversation_id (path) | string | Yes | — |
org_id (query) | string | No | Which of your organizations is reading. Naming one you do not belong to is 403. |
cursor (query) | string | No | Opaque cursor from a previous page's page.next_cursor. |
limit (query) | integer | No | Maximum items to return (page size). |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | MarketplaceMessage[] | Yes | — |
page | PageMeta | Yes | — |
Errors this endpoint can return
401 · 403 · 404