support

POST `/v1/webhooks/inbound-email`

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

Autentikasi

Titik akhir ini bersifat publik. Titik akhir ini tidak memerlukan kredensial maupun organisasi—inilah yang dibaca oleh situs pemasaran kami sendiri dan mesin jawaban AI.

Endpoint ini tidak memerlukan id organisasi. Kunci Anda telah mengidentifikasi organisasi tempatnya berafiliasi, dan respons akan dibatasi untuk organisasi tersebut.

Coba

Ganti apa pun di dalam tanda kurung sudut dengan nilai Anda sendiri, dan placeholder kunci dengan kunci dari dasbor Anda.

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

Sudah masuk? Konsol API di dasbor Anda akan mengisi ID organisasi asli dan kunci Anda sendiri, serta menjalankan permintaan terhadap API langsung sehingga Anda dapat melihat respons aktualnya. Buka titik akhir ini di konsol API

Detail

**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.

Parameter

Nama	Jenis	Wajib	Tentang apa ini
`X-Zinn-Timestamp (header)`	`string`	Ya	Unix seconds. Inside the signed material; skew-bounded to five minutes.
`X-Zinn-Signature (header)`	`string`	Ya	`sha256=<hex>` HMAC over `"<timestamp>\n<body>"`.

Isi permintaan

Nama	Jenis	Wajib	Tentang apa ini
`from`	`string`	Ya	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`	Tidak	—
`message_id`	`string`	Ya	The message's own `Message-ID`. Stored, and unique, so a redelivery cannot append twice.
`in_reply_to`	`string`	Tidak	Carries the signed ticket token when the customer replied to one of our notifications.
`references`	`string`	Tidak	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`	Tidak	—
`text`	`string`	Tidak	The message body. Quoted history is trimmed engine-side and the result is length-bounded.

Tanggapan

Nama	Jenis	Wajib	Tentang apa ini
`ticket_id`	`string`	Ya	—
`duplicate`	`boolean`	Ya	This exact message had already been filed — a success, not an error.
`sender_verified`	`boolean`	Ya	Whether the sender is a known address on the ticket's org. `false` still files the message, flagged for staff.
`reopened`	`boolean`	Ya	Whether filing it moved a `solved` ticket back to `open`.

Kesalahan yang dapat dikembalikan oleh titik akhir ini

400 · 422 · 503

POST /v1/webhooks/inbound-email