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 the… |
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… |
このエンドポイントが返すエラー
401 · 404 · 422 · 503