hosting

POST `/v1/site-events/ingest`

Receive a site's report about its own changes (signed webhook).

身份验证

此端点是公开的。它不需要任何凭据或组织——这是我们自己的营销网站和 AI 问答引擎所读取的内容。

此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。

免费试用

将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。

curl -X POST https://api.zinndigital.com/v1/site-events/ingest \
  -H "Content-Type: application/json" \
  -d '{ "site": <string> }'

已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。在 API 控制台中打开此端点

详细信息

What a site's Zinn® plugin POSTs when something changed on it — a plugin activated or deactivated, core or a theme updated, a theme switched — plus the PHP version it is running. **Machine-to-machine; there is no principal.** WordPress is talking, not a person, so there is no session, no API key and no organisation header. Authentication is an **HMAC-SHA256** over `"<timestamp>\n<body>"` in `X-Zinn-Cache-Signature` (`sha256=<hex>`), with `X-Zinn-Cache-Timestamp` carrying the unix seconds — the same scheme the plugin already uses for its cache-purge mirror. **The secret is derived, never stored.** The engine resolves `site` to a hosted site by primary domain, derives that site's webhook secret from the platform master key, and compares in constant time. The organisation comes from the **resolved site**: a valid signature proves the sender holds that site's secret and proves nothing whatsoever about any other tenant. **Every refusal is uninformative on purpose.** An unknown hostname is a bare `404` and a bad signature a bare `401`, because a chattier answer would tell anyone who can guess a hostname which domains this platform hosts. **Idempotent.** WordPress fires some of these hooks more than once per change and the POST is fire-and-forget, so a duplicate delivery is accepted with `stored: 0` rather than refused — replay safety lives in the database.

参数

名称	类型	必填	内容简介
`X-Zinn-Cache-Timestamp (header)`	`string`	是	Unix seconds. Signed as part of the material, which is what makes the replay window meaningful — a signature over the body alone could be replayed for ever with a fresh header.
`X-Zinn-Cache-Signature (header)`	`string`	是	`sha256=<hex>`.

请求正文

名称	类型	必填	内容简介
`site`	`string`	是	The site's own `home_url()`. An untrusted claim — it selects which site's derived secret the signature is checked against, and nothing more. The organisation is taken from t…
`php_version`	`string`	否	The PHP version the site is running. The engine raises a `php_version_changed` event when it differs from the last one reported — a change is detectable by comparison rather…
`events`	`object[]`	否	A batch. WordPress bulk-updating 40 plugins fires one `upgrader_process_complete` describing all of them, so a batch is the normal case, not the edge case. `deploy` is rejected…

响应

名称	类型	必填	内容简介
`accepted`	`boolean`	是	—
`stored`	`integer`	是	How many rows were new. A duplicate delivery is accepted with `0` rather than refused: WordPress fires some of these hooks more than once per change and the POST is fire-and…

此端点可能返回的错误

401 · 404 · 422 · 503

POST /v1/site-events/ingest