support

POST `/v1/webhooks/inbound-email`

Ingest a customer's support reply from the mail edge.

Autentificare

Acest punct final este public. Nu necesită nicio acreditare și nicio organizație – este ceea ce citesc propriul nostru site de marketing și motoarele de răspuns AI.

Acest endpoint nu necesită un ID de organizație. Cheia ta identifică deja organizația căreia îi aparține, iar răspunsul este limitat la aceasta.

Încearcă

Înlocuiți tot ce se află între paranteze unghiulare cu propriile valori și substituentul cheie cu o cheie din tabloul de bord.

curl -X POST https://api.zinndigital.com/v1/webhooks/inbound-email \
  -H "Content-Type: application/json" \
  -d '{ "from": <string>, "message_id": <string> }'

Autentificat? Consola API din panoul de control îți completează ID-ul real al organizației și propria cheie și rulează cererea în API-ul live, astfel încât să poți vedea răspunsul efectiv. Deschideți acest punct final în consola API

Detalii

**Unauthenticated by design** — the caller is a Cloudflare Email Routing Worker with no Zinn® credential, so an HMAC over `"<timestamp>\n<body>"` in `X-Zinn-Signature` *is* the authentication. The timestamp is inside the signed material and its skew is bounded, so a captured request cannot be replayed later. This is the inbound half of support email. Before it existed the platform sent notifications from an address that accepted mail and discarded it: a customer replied, nothing happened, and neither they nor the waiting staff member was told. The ticket is resolved from a **signed token inside the `Message-ID`** we set on the outbound notification — nothing in the body, the `From` address or any other header selects a tenant, because all of those are chosen by whoever sent the mail. Redelivery is the normal case, not the exception: email is at-least-once and a lost response guarantees a retry, so a message already filed answers `200` with `duplicate: true` rather than appending a second copy. ⛔ Unlike the gateway webhooks, a message that **cannot be routed is answered `422`**, not `200`. A 2xx tells the Worker to accept the mail, and an accepted message that reaches no ticket is the exact defect this endpoint exists to remove; `422` makes the Worker reject it so the sender's own mail server bounces it back to the customer.

Parametri

Nume	Tip	Obligatoriu	Ce este
`X-Zinn-Timestamp (header)`	`string`	Da	Unix seconds. Inside the signed material; skew-bounded to five minutes.
`X-Zinn-Signature (header)`	`string`	Da	`sha256=<hex>` HMAC over `"<timestamp>\n<body>"`.

Corp cerere

Nume	Tip	Obligatoriu	Ce este
`from`	`string`	Da	The envelope sender. Forgeable, and treated as such — it is checked against the ticket's org and the answer becomes a flag, never a permission.
`to`	`string`	Nu	—
`message_id`	`string`	Da	The message's own `Message-ID`. Stored, and unique, so a redelivery cannot append twice.
`in_reply_to`	`string`	Nu	Carries the signed ticket token when the customer replied to one of our notifications.
`references`	`string`	Nu	The full thread chain. Searched as well as `in_reply_to`, because a reply to the third message in a thread puts our id here and not there.
`subject`	`string`	Nu	—
`text`	`string`	Nu	The message body. Quoted history is trimmed engine-side and the result is length-bounded.

Răspuns

Nume	Tip	Obligatoriu	Ce este
`ticket_id`	`string`	Da	—
`duplicate`	`boolean`	Da	This exact message had already been filed — a success, not an error.
`sender_verified`	`boolean`	Da	Whether the sender is a known address on the ticket's org. `false` still files the message, flagged for staff.
`reopened`	`boolean`	Da	Whether filing it moved a `solved` ticket back to `open`.

Erori pe care le poate returna acest punct final

400 · 422 · 503

POST /v1/webhooks/inbound-email