API archive entry · source-reported

Svix API

Welcome to the Svix API documentation! Useful links: Homepage | Support email | Blog | Slack Community # Introduction This is the reference documentation and schemas for the Svix webhook service API. For tutorials and other documentation please refer to the documentation. ## Main concepts In Svix you have four important entities you will be interacting with: - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint. ## Authentication Get your authentication token (`AUTH_TOKEN`) from the Svix dashboard and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. ## Code samples T

Provider / source website

Archive history

This history reflects directory observations and owner review, not a provider release log.

  1. First observed: Sep 20, 2026
  2. Last directory-field change: Sep 20, 2026
  3. Current source observation: Sep 20, 2026

Published source events

added

Sep 20, 2026 · Added from an approved API directory.

Where to check product changes

Use the provider documentation and status channels for releases, breaking changes, and outages.

Source reference

APIs.guru OpenAPI Directory

This page separates source-reported facts from questions that need live provider verification.