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 Connector API

Connectors allow you to connect applications to external services.

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

Tagged areas include Connector. 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 13 operations across 8 paths, and defines 21 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.

13 operations 8 paths 21 schemas 1 DELETE3 GET1 PATCH5 POST3 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 Connector 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 13

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

Connector 13

Connectors allow you to connect applications to external services.

GET
/api/v1/connector
List Connectors
v1.connector.list 4 params → 200400401403404409422429
POST
/api/v1/connector
Create Connector
v1.connector.create 1 param body → 201400401403404409422429
GET
/api/v1/connector/{connector_id}
Get Connector
v1.connector.get 1 param → 200400401403404409422429
PUT
/api/v1/connector/{connector_id}
Upsert Connector
v1.connector.update 1 param body → 200201400401403404409422
DELETE
/api/v1/connector/{connector_id}
Delete Connector
v1.connector.delete 1 param → 204400401403404409422429
PATCH
/api/v1/connector/{connector_id}
Patch Connector
v1.connector.patch 1 param body → 200400401403404409422429
GET
/api/v1/connector/{connector_id}/options
Get Connector Options
v1.connector.options.get 1 param → 200204400401403404409422
PUT
/api/v1/connector/{connector_id}/options
Set Connector Options
v1.connector.options.set 1 param body → 200400401403404409422429
POST
/api/v1/connector/simulate
Simulate
v1.connector.simulate 1 param body → 200400401403404409422429
POST
/api/v1/connector/oauth/slack
Authorize Slack
v1.connector.oauth.slack 1 param body → 200400401403404409422429
POST
/api/v1/connector/oauth/discord
Authorize Discord
v1.connector.oauth.discord 1 param body → 200400401403404409422429
POST
/api/v1/connector/oauth/hubspot
Authorize Hubspot
v1.connector.oauth.hubspot 1 param body → 200400401403404409422429
PUT
/api/v1/app/{app_id}/endpoint/{endpoint_id}/connector/oauth/hubspot
Update Hubspot Oauth Config
v1.endpoint.update-hubspot-oauth-config 2 params body → 204400401403404409422429

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are ConnectorOut (15 properties), ConnectorIn (10 properties), ConnectorUpdate (8 properties), ConnectorPatch (8 properties). Each schema is shown below with its type and property counts.

TransformationSimulateIn
object
4 properties 3 required
ConnectorAuthenticationMethod
string
ConnectorOut
object
15 properties 11 required
ConnectorUpdate
object
8 properties 1 required
CustomConnectorOptions
object
2 properties
TransformationHttpMethod
string
TransformationSimulateOut
object
4 properties 3 required
HttpErrorOut
object
2 properties 2 required
OAuthPayloadOut
object
3 properties
HTTPValidationError
object
1 property 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
Ordering
string
Defines the ordering in a listing of results.
ListResponse_ConnectorOut_
object
4 properties 3 required
HubspotOauthConfigIn
object
1 property 1 required
ConnectorOptions
ConnectorKind
string
ConnectorPatch
object
8 properties
ConnectorIn
object
10 properties 2 required
OAuthPayloadIn
object
2 properties 2 required
ConnectorProduct
string
IncomingWebhookPayloadOut
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

svix-connector-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 Endpoint API
Svix Environment API
Svix Event API
Svix Event Type 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 Connector 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.