Base path:
https://api.aegis-kyt.com/v1/webhooks · Auth: X-API-Key: aeg_<48 chars>Register a subscription
urlmust start withhttps://(orhttp://localhostfor dev).eventsmust be a non-empty subset of the allowlist (see Event schemas for the current set).failure_thresholdis optional, defaults to5, range1..50. Auto-disable kicks in after this many consecutivegave_updeliveries.
List subscriptions
secret is never returned by this endpoint or by GET /v1/webhooks/{id}.
Get one subscription
Update — toggle / change events
is_active: true also resets consecutive_failures to
zero, so this is the canonical way to re-enable a subscription
after auto-disable.
Both fields are optional — send only what you want to change.
Delete
aegis_webhook_deliveries history; you can’t get
this data back. Pending deliveries already queued in
BackgroundTasks may still fire once after delete (best-effort).
Send a synthetic test event
- We build a synthetic payload for the requested
event_type— sentinel ids (00000000-…), a top-levelsynthetic: truefield, and minimum-viable fields per event_type. - We sign + POST it to just this subscription’s URL (the
only_subscription_idfilter — your other subs won’t see it). - Retry policy is the same as production events: 5 attempts over ~1 h. This intentionally lets you verify your retry / idempotency handling, not just first-call signature checks.
Request body
Errors
Recipes
Verify your handler before going live
Re-enable after auto-disable
consecutive_failures to 0)
