marketplace

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

Send a message on an order.

Svi marketplace krajnji točke

Autentifikacija

Pošaljite API ključ kao bearer token. Ova krajnja točka ne navodi određenu dozvolu u specifikaciji, stoga dajte svom ključu najmanje što mu je potrebno i provjerite odgovor umjesto da pretpostavljate.

Ova krajnja točka ne prihvaća ID organizacije. Vaš ključ već identificira organizaciju kojoj pripada, a odgovor je ograničen na nju.

Isprobajte

Zamijenite sve unutar šiljastih zagrada svojim vlastitim vrijednostima, a rezervirano mjesto za ključ s ključem iz vaše nadzorne ploče.

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 nadzornoj ploči automatski unosi stvarni ID vaše organizacije i vaš vlastiti ključ te šalje zahtjev prema aktivnom API-ju kako biste mogli vidjeti stvarni odgovor. Otvori ovu krajnju točku u API konzoli

Pojedinosti

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Što je to
sale_id (path)stringDa

Tijelo zahtjeva

NazivVrstaObaveznoŠto je to
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Što je to
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

Pogreške koje ova krajnja točka može vratiti

401 · 404 · 422