How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Svix Event Type API

Event types are identifiers denoting the type of message being sent. Event types are primarily used to decide which events are sent to which endpoint.

Svix Event Type API is one of 29 APIs that Svix publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Event Type. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and rate-limit docs.

This API exposes 10 operations across 5 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version 1.922.0.

Requests are made against 5 base URLs: https://api.eu.svix.com, https://api.us.svix.com, https://api.ca.svix.com, https://api.au.svix.com, https://api.in.svix.com.

10 operations 5 paths 19 schemas 1 DELETE3 GET1 PATCH3 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.922.0
Base URL
https://api.svix.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Svix Event Type API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer).

  • HTTPBearer — HTTP Bearer token passed in the Authorization header

Paths & Operations 10

Across 5 paths, the API surfaces 10 operations — 1 DELETE, 3 GET, 1 PATCH, 3 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Event Type 10

Event types are identifiers denoting the type of message being sent. Event types are primarily used to decide which events are sent to which endpoint.

GET
/api/v1/event-type
List Event Types
v1.event-type.list 5 params → 200400401403404409422429
POST
/api/v1/event-type
Create Event Type
v1.event-type.create 1 param body → 201400401403404409422429
POST
/api/v1/event-type/import/openapi
Event Type Import From Openapi
v1.event-type.import-openapi 1 param body → 200400401403404409422429
GET
/api/v1/event-type/{event_type_name}
Get Event Type
v1.event-type.get 1 param → 200400401403404409422429
PUT
/api/v1/event-type/{event_type_name}
Upsert Event Type
v1.event-type.update 1 param body → 200201400401403404409422
DELETE
/api/v1/event-type/{event_type_name}
Delete Event Type
v1.event-type.delete 2 params → 204400401403404409422429
PATCH
/api/v1/event-type/{event_type_name}
Patch Event Type
v1.event-type.patch 1 param body → 200400401403404409422429
GET
/api/v1/event-type/{event_type_name}/retry-schedule
Get Retry Schedule
v1.event-type.get-retry-schedule 1 param → 200400401403404409422429
PUT
/api/v1/event-type/{event_type_name}/retry-schedule
Set Retry Schedule
v1.event-type.set-retry-schedule 1 param body → 200400401403404409422429
POST
/api/v1/event-type/export/openapi
Event Type Export From Openapi
v1.event-type.export-openapi 1 param → 202400401403404409422429

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are EventTypeOut (10 properties), EventTypeIn (8 properties), EventTypeUpdate (7 properties), EventTypeFromOpenApi (7 properties). Each schema is shown below with its type and property counts.

EventTypeIn
object
8 properties 2 required
EventTypeImportOpenApiOut
object
1 property 1 required
ListResponse_EventTypeOut_
object
4 properties 3 required
BackgroundTaskStatus
string
RetrySchedule
array
EventTypeImportOpenApiOutData
object
2 properties 1 required
EventTypeFromOpenApi
object
7 properties 3 required
HttpErrorOut
object
2 properties 2 required
ExportEventTypeOut
object
4 properties 4 required
HTTPValidationError
object
1 property 1 required
EventTypePatch
object
7 properties
ValidationError
object
Validation errors have their own schema to provide context for invalid requests eg. mismatched types and out of bounds values. There may be any number of these…
3 properties 3 required
Duration
object
2 properties 2 required
BackgroundTaskType
string
Ordering
string
Defines the ordering in a listing of results.
RetryScheduleInOut
object
1 property
EventTypeUpdate
object
7 properties 1 required
EventTypeImportOpenApiIn
object
Import a list of event types from webhooks defined in an OpenAPI spec. The OpenAPI spec can be specified as either spec given the spec as a JSON object, or as…
4 properties
EventTypeOut
object
10 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

svix-event-type-api-openapi.yml Raw ↑

Other APIs Svix publishes across the network.

Svix Open Source Server API
Svix Application API
Svix Authentication API
Svix Background Task API
Svix Connector API
Svix Endpoint API
Svix Environment API
Svix Event API
Svix Health API
Svix Ingest Endpoint API
Svix Ingest Source API
Svix Integration API
Where this information came from

This is an independent, third-party profile of Svix Event Type API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.