hosting
POST /v1/connector/diagnostics
A support report a site owner chose to send — called by any Zinn® WordPress plugin.
身份验证
此端点是公开的。它不需要任何凭据或组织——这是我们自己的营销网站和 AI 问答引擎所读取的内容。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织,且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值,并将键占位符替换为您仪表板中的一个键。
curl -X POST https://api.zinndigital.com/v1/connector/diagnostics \
-H "Content-Type: application/json" \
-d '{ "plugin": <string>, "report": <object> }'已登录?您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥,并针对实时 API 运行请求,以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
⚖️ Owner ruling 2026-09-08, asked directly: the plugin shows the customer exactly what will be sent, redacted, before they press send. Declared secrets are omitted from the payload entirely rather than blanked, and the preview is the same bytes as the request body. ⛔ Unauthenticated by design. The customer most in need of sending a report is the one whose credential has just been revoked, so requiring the token would refuse exactly the population the feature exists for. A token, when present, ATTRIBUTES the report to an org and opens a real support ticket on that org's queue; without one the report is logged against the returned reference for an agent to find. The report is stored and never executed, never rendered as markup and never used to look anything up — it is written by PHP on a server we do not control.
请求正文
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
plugin | string | 是 | The plugin slug that built the report. |
report | object | 是 | The report body, as previewed to the customer. |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
received | boolean | 是 | — |
reference | string | 是 | The support reference to quote. Returned even if the ticket could not be opened. |
此端点可能返回的错误
413 · 422 · 429