Webhooks

Requires Elite

With webhooks, Notory calls your systems: on events (e.g., asset.created), Notory sends an HMAC-signed HTTP POST to a URL you configure — ideal for automation, ticketing systems, or data synchronization. Webhooks are tenant-bound, the signing secret is shown only once, and every delivery is recorded in a delivery log.

In this section

• How do I set up a webhook? — URL, events, secret, and the first test
• What events are there? — the events actually triggered and the payload format
• How do I verify the signature? — verifying HMAC-SHA256 (with code examples)
• What happens on delivery failures? — timeout, delivery log, and retry strategy

Prerequisites

Webhooks require the Elite plan (feature webhooks) — below that, every /webhooks endpoint responds with 403 (“Webhooks are only included in the Elite license.”). The Administrator role is allowed to manage them. The target URL must be reachable via HTTPS from the Notory server.

Related topics

• API Tokens — the reverse direction: your systems call Notory
• Module Licensing — check your plan and unlock modules
• Assets — Create an asset — triggers the asset.created event