Built by Metorial, the integration platform for agentic AI.
Retrieve the custom HTTP headers configured for a webhook endpoint, including the names of sensitive headers that Svix redacts.
Create a new consumer application in Svix. Applications represent your customers and are the target for webhook messages. Assign a custom UID (e.g., your internal customer ID) to enable stateless usage without storing Svix IDs.
Create a new webhook endpoint for an application. Endpoints are target URLs that receive webhook messages. Configure event type filtering, channels, and custom headers.
Check whether a message with the given event type and channels would be sent to any active endpoint before creating it.
Retrieve details of a specific consumer application by ID or UID. Returns the application's name, metadata, rate limit, and timestamps.
Bulk-recover all failed messages for an endpoint since a given date. This resends all messages that have exhausted their retry attempts. Use this after an outage or endpoint misconfiguration to replay missed webhooks.
Get delivery statistics for a specific endpoint including counts of successful, pending, failed, and sending attempts. Also retrieves the endpoint's signing secret for webhook verification.
Permanently delete a consumer application and all its associated endpoints and messages. This action cannot be undone.
Retrieve the JavaScript transformation configured for an endpoint and whether it is enabled.
Update an existing consumer application's name, UID, rate limit, or metadata. Provide the application ID or UID to identify which application to update.
List registered event types in your Svix environment. Event types categorize webhook messages and allow consumers to subscribe to specific events.
Delete the stored payload for a message while preserving delivery metadata. Use this for retention and privacy workflows.
Send a webhook message to a specific application. The message will be dispatched to all matching endpoints of that application. Optionally auto-create the application if it doesn't exist by including application details.
Retrieve a webhook message by Svix message ID or event ID. Optionally include the payload content for debugging or audit workflows.
List delivery attempts targeting a specific endpoint across all messages. Useful for diagnosing endpoint health and delivery patterns.
Rotate an endpoint's webhook signing secret. Provide a specific secret or omit it to let Svix generate one.
Retrieve a webhook endpoint's URL, filtering, throttle, status, metadata, and timestamps by ID or UID.
List delivery attempts for a specific message. Shows the status, response, and endpoint for each attempt. Use this to debug delivery failures or verify successful delivery.
Archive (soft-delete) an event type. Archived event types are hidden from consumers but can still be referenced by existing messages.
Set, unset, enable, or disable the JavaScript transformation associated with an endpoint.
Retrieve an event type by name, including schemas, feature flags, grouping, and lifecycle state.
Retrieve an endpoint's webhook signing secret for signature verification.
Generate a short-lived App Portal URL for a specific application. The portal lets your customers manage their endpoints, debug delivery, and inspect/replay past webhooks — all without needing a Svix account.
Update an existing webhook endpoint's URL, event type filters, channels, rate limit, or other configuration.
Create or update Svix event types from an OpenAPI document's webhooks section. Supports dry runs to preview changes without modifying event types.
List consumer applications in your Svix environment. Applications represent your customers, each receiving their own webhook messages. Use this to browse or search for applications before managing their endpoints or messages.
List all webhook endpoints for a specific application. Returns endpoint URLs, filtering configuration, and status.
List webhook messages sent to an application. Filter by event type, channel, or time range. Use this to audit message history or debug delivery issues.
Permanently delete a webhook endpoint from an application. The endpoint will no longer receive messages.
Replace the custom HTTP headers sent with webhook deliveries for an endpoint.
Update an event type's description, schemas, archive/deprecation state, feature flags, or group name.
Register a new event type in Svix. Event types are the primary way for webhook consumers to configure which events they receive. Optionally include a JSONSchema (Draft 7) to define the expected payload shape.
Manually resend a specific message to a specific endpoint. Use this to retry a single failed delivery without recovering all messages.