Website logo
Request an API key
⌘K
🚀Introduction
🏢Org Set Up
🏄Creator Onboarding
🛠️Stream Creation
🖥️Dashboard
🎙️Streams
📽️Creator Audio and Video
📚Media Integration
🗨️Chat
📈Polls, Points, & Leaderboards
🤙Guest Call-In
🤫Moderator tools
🖼️Picture-In-Picture
💰Monetization
🏦Tipping or In-App purchases
✋Paywalls
🛒Products (Live Shopping)
💵Ads
🌐Integrations & SDKs
🎛️API
Android SDK
iOS SDK
Javascript SDK
🎨Custom Themes
📊SDK Analytics
🔑Single Sign-On (SSO) (BETA)
🔔Webhooks (BETA)
👭Social Features
📽️Recordings & Content Management
🏷️Custom Fields & Tags
📜Changelog
⌛Usage Limits & Recommendations
Docs powered by Archbee
Integrations & SDKs

Webhooks (BETA)

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 some technology provided by Svix to support our webhooks.



Updated 03 Mar 2023
PREVIOUS
Single Sign-On (SSO) (BETA)
NEXT
Adding Endpoints
Docs powered by Archbee
TABLE OF CONTENTS
Introduction
Webhooks Consumption 101​
HotMic Webhooks
Docs powered by Archbee