Add Svix to your AI agent

Create a new event type in Svix or unarchive an existing one. Event types are identifiers (like 'order.created', 'user.signup') that categorize the webhooks your application sends. Use period-delimited naming to group related events. Both 'name' and 'description' are required. Returns HTTP 409 if the event type already exists.

Tool to delete an event type. Use when you need to archive or permanently expunge a specific event type after confirming its name.

Retrieve details of a specific event type by its name. Use this to inspect an existing event type's configuration, schema, and status. Event types define the categories of events that can be sent through Svix webhooks.

Tool to retrieve a list of all event types. Use when you need to inspect available event types, optionally including their JSON schemas. Use after authenticating the client.

Update an existing event type's description, schema, feature flags, or archive status. Use this to modify event type configuration. The event type must already exist - use List Event Types or Get Event Type to find valid event type names.

Tool to create a new integration for a specific application. Use after confirming the application ID.

Permanently delete an integration from a Svix application. This is a destructive operation that cannot be undone. Use when removing webhook integrations that are no longer needed. Requires both the application ID and the integration ID. Use 'List Integrations' first if you need to find the integration_id.

Tool to retrieve details of a specific integration. Use after confirming app_id and integration_id.

Tool to list all integrations for a specific application. Use after confirming the application ID, supporting pagination via limit and iterator. Use when you need to enumerate integrations.

Tool to update an existing integration by ID. Use when you need to modify an integration's name or feature flags.

Tool to create a new message for a specific application in Svix. Use after confirming app ID and event details.

Tool to retrieve details of a specific message by its ID. Use when you need message metadata and status after dispatch.

Tool to list all messages for a specific application. Use when you need to fetch or paginate messages after obtaining the application ID.

Tool to retrieve details of a specific message attempt. Use after confirming app_id, msg_id, and attempt_id.

Tool to list all delivery attempts for a specific message. Use after confirming message ID to debug attempts.

Tool to recover messages that failed to send to an endpoint. Use when you need to retry webhook delivery for failed events after identifying delivery failures.

Tool to replay missing webhooks for a specific endpoint. Use when some webhooks failed or were lost and need to be resent.

Tool to retrieve the secret for a specific endpoint. Use after confirming app_id and endpoint_id.

Tool to rotate the signing secret key for an endpoint. Use when you need to invalidate the current secret and generate or supply a new one. Call after confirming app_id and endpoint_id.

Tool to send a test message for a specific event type to an endpoint. Use after setting up an endpoint to verify its configuration. Note: the endpoint's filter_types must include the event_type being tested; otherwise real events will not be delivered even if the example message sends successfully.

Tool to retrieve basic statistics for a specific endpoint. Use after confirming app_id and endpoint_id.

Tool to retrieve transformation settings for a specific endpoint. Use after confirming app_id and endpoint_id.

Tool to set or update transformation settings for an endpoint. Use when you need to configure or toggle an endpoint's transformation code after creation.

Tool to completely replace headers for a specific endpoint. Use when you need to set a full new header mapping.

Creates a new Svix Ingest source for receiving webhooks from external providers. A source generates an ingest URL that you can share with a webhook provider (e.g., GitHub, Stripe) as the destination for their webhooks. Svix will verify signatures based on the source type and forward the webhooks to your configured endpoints. Use 'genericWebhook' type to skip signature verification for providers not natively supported.