marketplace
POST /v1/marketplace/orders/{sale_id}/messages
Send a message on an order.
Authenticatie
Stuur een API-sleutel mee als bearer token. Dit eindpunt vermeldt geen specifieke toestemming in de specificatie, dus geef uw sleutel de minimale rechten die nodig zijn en controleer het antwoord in plaats van zomaar wat aan te nemen.
Dit eindpunt vereist geen organisatie-id. Uw sleutel identificeert al de organisatie waartoe deze behoort, en het antwoord is hierop afgestemd.
Probeer het
Vervang alles tussen punthaakjes door uw eigen waarden en de sleutelplaatsvervanger door een sleutel uit uw dashboard.
curl -X POST https://api.zinndigital.com/v1/marketplace/orders/{sale_id}/messages \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ "body": <string> }'Ingelogd? De API-console in je dashboard vult je echte organisatie-id en je eigen sleutel in, en voert het verzoek uit tegen de live API zodat je de daadwerkelijke respons kunt zien. Open dit eindpunt in de API-console
Details
docs/133 D26. The on-platform contact policy applies and is **proportionate**: a message may be sent as written, sent and flagged quietly, sent with contact details masked, or held for review. There is no rung that refuses to send — a hard block is what generates the false positives honest sellers leave over, and they do not complain first. After an order exists, exchanging details is often the work itself — a guest post needs the target URL and the anchor, an asset transfer needs the registrar and the DNS — so the policy leans far less here than on a pre-sales enquiry, and least of all on an asset transfer. `held` is reported to the sender. It is the one case where "sent" would be a lie.
Parameters
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
sale_id (path) | string | Ja | — |
Aanvraaglichaam
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
body | string | Ja | — |
locale | string | Nee | — |
attachments | object[] | Nee | Refused entirely on a pre-sales thread: an attachment bypasses text scanning and we have no OCR, so on the one surface where nobody has paid there are no files. |
Reactie
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
id | string | Ja | — |
body | string | Ja | What the reader sees — the masked form where the policy masked it. The original is always kept in the order record and is what a dispute reads; it is not in this payload, becaus… |
mine | boolean | Ja | — |
from_staff | boolean | Nee | — |
source_locale | string | Nee | BCP-47. Participants write in their own language; a message is translated FOR THE READER and the original is always shown, never replaced. |
masked | boolean | Nee | — |
policy_notice | string | Nee | A message KEY, rendered in every locale by the client. Set only for the SENDER of a masked message — telling the recipient "they tried to give you an email address" would be an… |
held | boolean | Nee | Only on the send response. The one case where reporting "sent" would be a lie. |
created_at | string | Ja | — |
Fouten die dit eindpunt kan retourneren
401 · 404 · 422