Webhooks
BetaHMAC-signed outbound webhooks with retries and a delivery log. Six research events fire today.
Plan availability. Webhook subscriptions belong to an Intelligence API key, and this is not switched on in any of our four published plans. Starter, Pro, Business and Enterprise all resolve to the same feature set and this one is off in all of them, so a subscription will not unlock it — it has to be enabled for your organisation by arrangement. Ask us before you plan around it.
- ✓HMAC-SHA256 signature over the payload, with event, delivery id and attempt headers
- ✓Six retries on a widening schedule out to 24 hours, then auto-disable after sustained failure
- ✓Delivery log per subscription showing every attempt
- ✓Rotate a subscription's signing secret
What it is.
Register an HTTPS endpoint and LexVio POSTs signed JSON to it, with the signature, the event name, a delivery id and the attempt number in the headers. Failures retry on a widening schedule — 30 seconds, 2 minutes, 10 minutes, an hour, six hours, a day — and a subscription that keeps failing is disabled rather than left hammering a dead endpoint. Every attempt is recorded and readable.
Be precise about what actually fires. Twelve event types can be subscribed to; six of them are emitted by live code, all of them research events — a thread created, saved, unsaved or deleted, and a memory created or deleted. The judgment, statute, cause-list, clause-benchmark and compliance-alert events are declared and subscribable and nothing publishes them. The product's own source says that is a promise it should not be making, and we agree.
Three steps.
End to end.
An HTTPS URL, checked against server-side request forgery on create and on update. The signing secret is returned once.
Subscribe to the event types you want. Check the list below for which of them actually fire.
Verify the HMAC-SHA256 signature over the body, then act. Read the delivery log to see every attempt.
What you get.
- ✓HMAC-SHA256 signature over the payload, with event, delivery id and attempt headers
- ✓Six retries on a widening schedule out to 24 hours, then auto-disable after sustained failure
- ✓Delivery log per subscription showing every attempt
- ✓Rotate a subscription's signing secret
- ✓Emitted today: research thread created / saved / unsaved / deleted, research memory created / deleted
- ✓Declared but never emitted: judgment created and updated, statute amended, cause-list entry, clause-benchmark updated, compliance alert raised
Quick answers.
No. There is no scan-complete event, and no deadline, document-share or AI-run event either. The six events that fire are research events.
We retry six times over 24 hours. After sustained failure the subscription is disabled. There is no manual replay endpoint — re-enable and wait for the next event.
No. Webhook subscriptions hang off an Intelligence API key, which is subject to the plan note above.
More in Workflow Automation.
53 ready-made agents — vendor onboarding, NDA quickscan, GSTR-2A reconciler, weekly compliance digest — install and run.
Define your own multi-step agent — AI calls, data queries, HTTP calls and notifications, run in sequence.
Not shipped. A cron expression can be saved on an agent, and nothing dispatches it.
A multi-step approval chain on a contract, routed by role and value — plus a review gate on AI output.