Webhooks

introduction webhooks consumption 101 ​ https //docs svix com/receiving/introduction#webhooks consumption 101 webhooks are how services notify each other of events at their core they are just a post request to a pre determined endpoint the endpoint can be whatever you want, and you can just add them from the ui you normally use one endpoint per service, and that endpoint listens to all of the event types for example, if you receive webhooks from acme inc , you can structure your url like https //www example com/acme/webhooks/ the way to indicate that a webhook has been processed is by returning a 2xx (status code 200 299) response to the webhook message within a reasonable time frame (15s) it's also important to disable csrf protection for this endpoint if the framework you use enables them by default another important aspect of handling webhooks is to verify the signature and timestamp when processing them hotmic webhooks hotmic uses webhooks to allow you to receive the following events stream events stream created stream live countdown stream ended moderation events user blocked