hosting
POST /v1/site-events/ingest
Receive a site's report about its own changes (signed webhook).
Ìfàṣẹ́pọ̀
Ojú-wọ̀n yìí jẹ́ ti gbogbo ènìyàn. Kò gba àmì ìdánimọ̀ kankan tàbí àgbájọ kankan — ohun tí ojú-wọ̀n ìpolówó wa àti àwọn ẹ̀rọ ìdáhùn AI ǹkà kọ́ ni.
Ojú abánisọ̀rọ̀ yìí kò gba id ajọ kankan. Kọ́kọ́rọ́ rẹ ti mọ ajọ ti o jẹ ti e, a o si fèsì nipa rẹ̀.
Gbiyanju rẹ
Rọ́pọ̀ èyíkéyìí nínú àwọn àmì ìtọ́ka < > pẹ̀lú iye tirẹ̀, àti àmì ìdánimọ̀ bọ́tìnnì náà pẹ̀lú bọ́tìnnì kan láti inú dásibọ̀ọ̀dù rẹ.
curl -X POST https://api.zinndigital.com/v1/site-events/ingest \
-H "Content-Type: application/json" \
-d '{ "site": <string> }'Ṣé o ti wọlé? Iwọ̀n api ní nú ìgbékalẹ̀ rẹ kún id àjọ gidi rẹ ati bọtini tirẹ, o si nṣiṣẹ ibeere na lòdì si api gidi ki o le rii esi gidi na. Ṣí ojú abáná yìí sílẹ̀ nínú kọnsólù API
Àwọn kúlẹ̀kúlẹ̀
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.
Àwọn ìpìlẹ̀
| Orúkọ | Iru | Tí a nílò | Kini o jẹ |
|---|---|---|---|
X-Zinn-Cache-Timestamp (header) | string | Bẹẹni | 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 | Bẹẹni | sha256=<hex>. |
Akoonu ibeere naa
| Orúkọ | Iru | Tí a nílò | Kini o jẹ |
|---|---|---|---|
site | string | Bẹẹni | 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 the… |
php_version | string | Bẹẹkọ | 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[] | Bẹẹkọ | 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… |
Idahun
| Orúkọ | Iru | Tí a nílò | Kini o jẹ |
|---|---|---|---|
accepted | boolean | Bẹẹni | — |
stored | integer | Bẹẹni | 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… |
Awọn aṣiṣe ti ibudo ipari yii le da pada
401 · 404 · 422 · 503