Webhook Endpoint Management

Svix stores the endpoints, secrets, and subscriptions your application uses to send event notifications. A Beam agent reads the endpoint registry when a new customer integration is requested, then registers or disables endpoints according to a rule your team approves, for example enabling delivery only after a customer confirms their receiving URL. It writes the endpoint status back and records the change. When an endpoint fails signature verification or points at an unfamiliar domain, the agent leaves it inactive and asks an engineer to confirm before any events are allowed to flow to it.

Failed Delivery Retries

Every webhook attempt in Svix carries a delivery status, response code, and retry history. A Beam agent watches for messages that exhaust their automatic retries, reads the failure detail, and applies your recovery rule: requeue transient network errors, and pause endpoints returning repeated authentication rejections. It updates the message state and posts a short summary to the owning team channel. Deliveries that fail because of a changed payload contract, or that affect a high value customer, are handed to a person who decides whether to replay them or contact the recipient directly.

Event Type Catalog

Svix keeps a catalog of the event types your service publishes, each with a schema and description. A Beam agent compares the catalog against a new release note, reads which events changed, and drafts catalog entries for events your team has approved for external use. It updates descriptions and marks deprecated types. Where a proposed event exposes fields that may carry personal or financial data, the agent stops and routes the entry to a reviewer, so no schema reaches subscribers until someone confirms the fields are safe to share.