a1-yandex-kit-webhookslisted

# A1 Yandex KIT — Webhooks ## Communication Before producing any user-facing message, read and apply [`../a1-yandex-kit/references/merchant-communication.md`](../a1-yandex-kit/references/merchant-communication.md) completely. Covers the Вебхуки tag of the Yandex KIT e-commerce API: subscribing HTTPS endpoints to order lifecycle notifications and managing those subscriptions. Key facts: - Callback URLs must be **HTTPS** — plain `http://` URLs are rejected. - Exactly **three event types** exist: `ORDER_STATUS_CHANGED`, `ORDER_PAYMENT_STATUS_CHANGED` and `ORDER_DELIVERY_STATUS_CHANGED`. - Creating a webhook (`CreateWebhook`) returns a signing `secret` that is shown **only once** — persist it immediately; it cannot be retrieved later (delete and recreate the webhook if lost). - **The signature algorithm is not documented by Yandex.** Use the secret to verify that incoming calls are authentic, but check the KIT community chat (https://t.me/+f9qV8snaY1pmM2Ji) or Yandex support for the current signing scheme before relying on any particular construction. - `ValidateWebhook` asks the API to POST a `WEBHOOK_VALIDATE` event to your URL — use it to test reachability after deploying the receiver. For authentication (`Authorization: Bearer <token>`), the base URL (`https://api.kit.yandex.net`, all paths under `/v1/`), the 3 rps rate limit and the `{code, message, trace_id}` error contract, see the `a1-yandex-kit` skill. ## Workflow Run the bundled scripts from this s