Send webhook events to SQS, EventBridge, and RabbitMQ · Svix

Our easy-to-use webhook API equips you to deliver a top-tier webhook experience.
Robust products for sending, receiving, and testing webhooks.
Join the Svix community and get support.
Svix is used by a variety of industries for different use cases.
The queue absorbs bursts, and their existing workers pick up events like any other message.
Customers set up queue destinations in the same portal they use for their webhook endpoints.
Customers don't have to expose an HTTPS endpoint to the internet. Events go straight to infrastructure they already secure.
Events go straight onto your customer's SQS queue, EventBridge bus, or RabbitMQ broker, where their existing consumers pick them up.
Each event becomes a message in your customer's SQS queue.
Publish events to your customer's EventBridge bus.
Publish events to your customer's RabbitMQ broker.
Each event arrives as its own message, with the event type and payload as JSON. A transformation can reshape the body into whatever their consumers expect.
Amazon SQS, Amazon EventBridge, and RabbitMQ. Your customers add them in the App Portal, next to their webhook endpoints.
For SQS, the queue URL plus an AWS region and credentials. For EventBridge, the event bus name or ARN and the same AWS details. For RabbitMQ, an AMQP connection URI, which can include a virtual host, and a routing key.
Every event is published with a source of svix-webhooks- followed by your Svix application ID, and a detail type your customer chooses, which defaults to application/json. Rules can match on either.
Yes. A transformation, a short JavaScript function, receives each batch and returns the exact message bodies to send, so they match the format your customer's consumers already expect.
No. You keep calling the same message API. Your customers configure how they want to receive them in the Application Portal.
© Svix Inc. All rights reserved. Svix® is a registered trademark of Svix Inc.