This section provides an overview of the main concepts of Svix and how to use them.| docs.svix.com
Because of the way webhooks work, attackers can impersonate services by simply sending a fake webhook to an endpoint. Think about it: it's just an HTTP POST from an unknown source. This is a potential security hole for many applications, or at the very least, a source of problems.| docs.svix.com
This section explains how to add and use multiple environments (e.g. dev, staging, and prod) from the same account.| docs.svix.com
Svix comes with a consumer application portal for your users (webhook consumers) that you can use out of the box. Your users can then use it to add endpoints, debug delivery, as well as inspect and replay past webhooks. This is the easiest way to get started, but you can alternatively use the API to build your own.| docs.svix.com
Transformations are a powerful Svix feature that allows the modification of certain webhook properties in-flight. When you enable Transformations, your customers can write JavaScript code on their endpoints that can change a webhook's HTTP method, target URL, and body payload.| docs.svix.com
This guide assumes your familiar with the basics of event types and the App Portal.| docs.svix.com
The recommended way to verify webhooks is using our official libraries as outlined in the How to Verify section.| docs.svix.com