marketplace

POST /v1/marketplace/orders/{sale_id}/messages

Send a message on an order.

Sve marketplace krajnje tačke

Autentifikacija

Pošaljite API ključ kao bearer token. Ova krajnja tačka ne navodi specifičnu dozvolu u specifikaciji, zato dodelite svom ključu minimum potrebnih ovlašćenja i proverite odgovor umesto da pretpostavljate.

Ovaj krajnji tačka ne prihvata ID organizacije. Vaš ključ već identifikuje organizaciju kojoj pripada, a odgovor je ograničen na nju.

Isprobajte

Zamenite bilo šta u uglastim zagradama sopstvenim vrednostima, a ključni placeholder sa ključem sa vaše kontrolne table.

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> }'

Prijavljeni ste? API konzola na vašoj kontrolnoj tabli automatski popunjava ID vaše stvarne organizacije i vaš sopstveni ključ, i izvršava zahtev nad API-jem uživo tako da možete videti stvarni odgovor. Otvorite ovu krajnju tačku u API konzoli

Detalji

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.

Parametri

NazivVrstaObaveznoŠta je ovo
sale_id (path)stringDa

Telo zahteva

NazivVrstaObaveznoŠta je ovo
bodystringDa
localestringNe
attachmentsobject[]NeRefused 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.

Odgovor

NazivVrstaObaveznoŠta je ovo
idstringDa
bodystringDaWhat 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…
minebooleanDa
from_staffbooleanNe
source_localestringNeBCP-47. Participants write in their own language; a message is translated FOR THE READER and the original is always shown, never replaced.
maskedbooleanNe
policy_noticestringNeA 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…
heldbooleanNeOnly on the send response. The one case where reporting "sent" would be a lie.
created_atstringDa

Greške koje ovaj krajnji tačka može da vrati

401 · 404 · 422