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 Message Attempt API

Attempts to deliver `Message`s to `Endpoint`s.

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

Tagged areas include Message Attempt. 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 9 operations across 9 paths, and defines 17 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.

9 operations 9 paths 17 schemas 1 DELETE7 GET1 POST

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 Message Attempt 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 9

Across 9 paths, the API surfaces 9 operations — 1 DELETE, 7 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Message Attempt 9

Attempts to deliver Messages to Endpoints.

GET
/api/v1/app/{app_id}/attempt/endpoint/{endpoint_id}
List Attempts By Endpoint
v1.message-attempt.list-by-endpoint 14 params → 200400401403404409422429
GET
/api/v1/app/{app_id}/attempt/endpoint/{endpoint_id}/count
Count Attempts By Endpoint
v1.message-attempt.count-by-endpoint 9 params → 200400401403404409422429
GET
/api/v1/app/{app_id}/attempt/msg/{msg_id}
List Attempts By Msg
v1.message-attempt.list-by-msg 14 params → 200400401403404409422429
GET
/api/v1/app/{app_id}/endpoint/{endpoint_id}/msg
List Attempted Messages
v1.message-attempt.list-attempted-messages 12 params → 200400401403404409422429
GET
/api/v1/app/{app_id}/msg/{msg_id}/endpoint
List Attempted Destinations
v1.message-attempt.list-attempted-destinations 4 params → 200400401403404409422429
GET
/api/v1/app/{app_id}/msg/{msg_id}/attempt/{attempt_id}/headers
Get Attempt Headers
v1.message-attempt.get-headers 3 params → 200400401403404409422429
GET
/api/v1/app/{app_id}/msg/{msg_id}/attempt/{attempt_id}
Get Attempt
v1.message-attempt.get 4 params → 200400401403404409422429
DELETE
/api/v1/app/{app_id}/msg/{msg_id}/attempt/{attempt_id}/content
Delete attempt response body
v1.message-attempt.expunge-content 3 params → 204400401403404409422429
POST
/api/v1/app/{app_id}/msg/{msg_id}/endpoint/{endpoint_id}/resend
Resend Webhook
v1.message-attempt.resend 4 params → 202400401403404409422429

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are MessageEndpointOut (15 properties), MessageAttemptOut (12 properties), EndpointMessageOut (11 properties), MessageOut (8 properties). Each schema is shown below with its type and property counts.

MessageAttemptOut
object
12 properties 11 required
ListResponse_MessageEndpointOut_
object
4 properties 3 required
CountOut
object
2 properties 2 required
HttpErrorOut
object
2 properties 2 required
MessageStatus
integer
The sending status of the message: - Success = 0 - Pending = 1 - Fail = 2 - Sending = 3 - Canceled = 4
MessageEndpointOut
object
15 properties 8 required
MessageAttemptHeadersOut
object
3 properties 2 required
MessageStatusText
string
ListResponse_EndpointMessageOut_
object
4 properties 3 required
StatusCodeClass
integer
The different classes of HTTP status codes: - CodeNone = 0 - Code1xx = 100 - Code2xx = 200 - Code3xx = 300 - Code4xx = 400 - Code5xx = 500
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
MessageOut
object
8 properties 4 required
MessageAttemptTriggerType
integer
The reason an attempt was made: - Scheduled = 0 - Manual = 1
EmptyResponse
object
EndpointMessageOut
object
A model containing information on a given message plus additional fields on the last attempt for that message.
11 properties 6 required
ListResponse_MessageAttemptOut_
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

svix-message-attempt-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 Endpoint API
Svix Ingest Source API
Where this information came from

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