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 Ingest Endpoint API

Configure where Svix Ingest sends messages.

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

Tagged areas include Ingest Endpoint. 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 11 operations across 6 paths, and defines 14 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.

11 operations 6 paths 14 schemas 1 DELETE5 GET1 PATCH2 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 Ingest Endpoint 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 11

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

Ingest Endpoint 11

Configure where Svix Ingest sends messages.

GET
/ingest/api/v1/source/{source_id}/endpoint
List Ingest Endpoints
v1.ingest.endpoint.list 4 params → 200400401403404409422429
POST
/ingest/api/v1/source/{source_id}/endpoint
Create Ingest Endpoint
v1.ingest.endpoint.create 2 params body → 201400401403404409422429
GET
/ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}
Get Ingest Endpoint
v1.ingest.endpoint.get 2 params → 200400401403404409422429
PUT
/ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}
Upsert Ingest Endpoint
v1.ingest.endpoint.update 2 params body → 200400401403404409422429
DELETE
/ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}
Delete Ingest Endpoint
v1.ingest.endpoint.delete 2 params → 204400401403404409422429
GET
/ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}/secret
Get Ingest Endpoint Secret
v1.ingest.endpoint.get-secret 2 params → 200400401403404409422429
POST
/ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}/secret/rotate
Rotate Ingest Endpoint Secret
v1.ingest.endpoint.rotate-secret 3 params body → 204400401403404409422429
GET
/ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}/headers
Get Ingest Endpoint Headers
v1.ingest.endpoint.get-headers 2 params → 200400401403404409422429
PUT
/ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}/headers
Set Ingest Endpoint Headers
v1.ingest.endpoint.update-headers 2 params body → 204400401403404409422429
GET
/ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}/transformation
Get Ingest Endpoint Transformation
v1.ingest.endpoint.get-transformation 2 params → 200400401403404409422429
PATCH
/ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}/transformation
Patch Ingest Endpoint Transformation
v1.ingest.endpoint.set-transformation 2 params body → 204400401403404409422429

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are IngestEndpointOut (10 properties), IngestEndpointIn (8 properties), IngestEndpointUpdate (7 properties), ListResponse_IngestEndpointOut_ (4 properties). Each schema is shown below with its type and property counts.

ListResponse_IngestEndpointOut_
object
4 properties 3 required
IngestEndpointTransformationPatch
object
2 properties
IngestEndpointTransformationOut
object
2 properties
HttpErrorOut
object
2 properties 2 required
IngestEndpointHeadersOut
object
2 properties 2 required
IngestEndpointSecretOut
object
1 property 1 required
IngestEndpointHeadersIn
object
1 property 1 required
IngestEndpointOut
object
10 properties 6 required
IngestEndpointSecretIn
object
1 property
HTTPValidationError
object
1 property 1 required
IngestEndpointIn
object
8 properties 1 required
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
IngestEndpointUpdate
object
7 properties 1 required
Ordering
string
Defines the ordering in a listing of results.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

svix-ingest-endpoint-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 Event Type API
Svix Health API
Svix Ingest Source API
Svix Integration API
Where this information came from

This is an independent, third-party profile of Svix Ingest Endpoint 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.