support

POST `/v1/tickets/deflect`

Knowledge-base articles and a live diagnosis, before a ticket is opened.

Autentikasi

Kirim kunci API sebagai token bearer. Kunci tersebut harus memiliki izin tickets.reply; kunci tanpa izin tersebut akan ditolak dengan status 403, bukan 404.

Tempat ID organisasi Anda dimasukkan

Titik akhir ini memerlukan org_id sebagai field dalam bodi JSON.

ID organisasi Anda berada di layar kunci API di dasbor Anda, di sebelah kunci itu sendiri. Itu adalah ID yang sama dalam setiap panggilan yang Anda buat.

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/tickets/deflect \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

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

The KB + AI in front of the ticket form (#2661). Given what the customer has typed so far, returns matching published KB articles and — when a site is named — findings from live checks against it, including whether its nameservers still point at us. ⛔ This never refuses to open a ticket and must never be made to. Everything it returns is offered; the form's submit button is unaffected. Requires `tickets.reply`. ⛔ `checks_incomplete` is `true` when a check could not run. "We found nothing wrong" and "we could not look" are different answers and the client must render them differently.

Isi permintaan

Nama	Jenis	Wajib	Tentang apa ini
`subject`	`string`	Tidak	—
`body`	`string`	Tidak	—
`site_id`	`object`	Tidak	The site they are asking about. When given, live checks run against it — including whether its nameservers still point at us.
`org_id`	`object`	Tidak	—

Tanggapan

Nama	Jenis	Wajib	Tentang apa ini
`articles`	`object[]`	Ya	—
`findings`	`TicketDeflectionFinding[]`	Ya	—
`applied`	`string[]`	Ya	Remedies applied automatically. ⛔ Only remedies on an explicit, audited allow-list are ever applied without a human.
`checks_incomplete`	`boolean`	Ya	⛔ True when a live check could not run. "We found nothing wrong" and "we could not look" are different answers and must render differently.
`incidents`	`TicketDeflectionIncident[]`	Ya	Open public incidents affecting this customer. ⛔ NOTHING HERE BLOCKS THE FORM — owner ruling 2026-08-24 was warn prominently, still let them submit. A customer with a genuinel…
`status_url`	`string`	Ya	The public status page in the reader's language, for the "follow this to resolution" link. ⛔ A separate origin with no shared fate with the platform (docs/121 §1), so it cannot…

Kesalahan yang dapat dikembalikan oleh titik akhir ini

401 · 403 · 422 · 429