support

POST `/v1/webhooks/inbound-email`

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

Autentifikatsiya

Bu oxirgi nuqta ochiq. U hech qanday ma'lumotnoma va tashkilotni talab qilmaydi — bu bizning o'z marketing saytimiz va sun'iy intellekt javob mexanizmlari o'qiydigan narsadir.

Bu yakuniy nuqta hech qanday tashkilot identifikatorini qabul qilmaydi. Sizning kalitingiz unga tegishli tashkilotni allaqachon aniqlaydi va javob shunga qarab cheklanadi.

Sinab ko'rish

Qavslardagi har qanday narsani o'z qiymatlaringiz bilan, kalit pleysxolderini эsa boshqaruv panelingizdagi kalit bilan almashtiring.

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

Tizimga kirganmisiz? Boshqaruv panelingizdagi API konsoli haqiqiy tashkilot ID raqamingiz va shaxsiy kalitingizni avtomatik to'ldiradi hamda haqiqiy javobni ko'rishingiz uchun so'rovni jonli API orqali bajaradi. Ushbu yakuniy nuqtani API konsolida oching

Tafsilotlar

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

Parametrlar

Nomi	Turi	Majburiy	Nima bu
`X-Zinn-Timestamp (header)`	`string`	Ha	Unix seconds. Inside the signed material; skew-bounded to five minutes.
`X-Zinn-Signature (header)`	`string`	Ha	`sha256=<hex>` HMAC over `"<timestamp>\n<body>"`.

Soʻrov tanasi

Nomi	Turi	Majburiy	Nima bu
`from`	`string`	Ha	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`	Yo'q	—
`message_id`	`string`	Ha	The message's own `Message-ID`. Stored, and unique, so a redelivery cannot append twice.
`in_reply_to`	`string`	Yo'q	Carries the signed ticket token when the customer replied to one of our notifications.
`references`	`string`	Yo'q	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`	Yo'q	—
`text`	`string`	Yo'q	The message body. Quoted history is trimmed engine-side and the result is length-bounded.

Javob

Nomi	Turi	Majburiy	Nima bu
`ticket_id`	`string`	Ha	—
`duplicate`	`boolean`	Ha	This exact message had already been filed — a success, not an error.
`sender_verified`	`boolean`	Ha	Whether the sender is a known address on the ticket's org. `false` still files the message, flagged for staff.
`reopened`	`boolean`	Ha	Whether filing it moved a `solved` ticket back to `open`.

Ushbu yakuniy nuqta qaytarishi mumkin bo'lgan xatolar

400 · 422 · 503

POST /v1/webhooks/inbound-email