Svix
DEVELOPER · DEVELOPER
Applications, endpoints, messages, and delivery attempts in the account they connected.
Acts as the person, not as itself
Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.
Credentials never touch the agent
Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.
Every call on the record
Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
svix_delete_api_v1_app_by_app_idWRITEDelete an application. via DELETE /api/v1/app/{app_id}
svix_delete_api_v1_app_by_app_id_destination_by_destination_idWRITEDelete a destination. via DELETE /api/v1/app/{app_id}/destination/{destination_id}
svix_delete_api_v1_app_by_app_id_endpoint_by_endpoint_idWRITEDelete an endpoint. via DELETE /api/v1/app/{app_id}/endpoint/{endpoint_id}
svix_delete_api_v1_app_by_app_id_integration_by_integ_idWRITEDelete an integration. via DELETE /api/v1/app/{app_id}/integration/{integ_id}
svix_delete_api_v1_app_by_app_id_msg_by_msg_id_attempt_by_attempt_id_contentWRITEDeletes the given attempt's response body. Useful when an endpoint accidentally returned sensitive content. The message can't be replayed or resent once its payload has been deleted or expired. via DELETE /api/v1/app/{app_id}/msg/{msg_id}/attempt/{attempt_id}/content
svix_delete_api_v1_app_by_app_id_msg_by_msg_id_contentWRITEDelete the given message's payload. Useful in cases when a message was accidentally sent with sensitive content. The message can't be replayed or resent once its payload has been deleted (or has expired). via DELETE /api/v1/app/{app_id}/msg/{msg_id}/content
svix_delete_api_v1_connector_by_connector_idWRITEDelete a connector. via DELETE /api/v1/connector/{connector_id}
svix_delete_api_v1_event_type_by_event_type_nameWRITEArchive an event type. Endpoints already configured to filter on an event type will continue to do so after archival. However, new messages can not be sent with it and endpoints can not filter on it. An event type can be unarchived with the create operation. via DELETE /api/v1/event-type/{event_type_name}
svix_delete_api_v1_operational_webhook_endpoint_by_endpoint_idWRITEDelete an operational webhook endpoint. via DELETE /api/v1/operational-webhook/endpoint/{endpoint_id}
svix_delete_api_v1_stream_by_stream_idWRITEDelete a stream. via DELETE /api/v1/stream/{stream_id}
svix_delete_api_v1_stream_by_stream_id_sink_by_sink_idWRITEDelete a sink. via DELETE /api/v1/stream/{stream_id}/sink/{sink_id}
svix_delete_api_v1_stream_event_type_by_nameWRITEDelete an event type. via DELETE /api/v1/stream/event-type/{name}
svix_delete_ingest_api_v1_source_by_source_idWRITEDelete an Ingest Source. via DELETE /ingest/api/v1/source/{source_id}
svix_delete_ingest_api_v1_source_by_source_id_endpoint_by_endpoint_idWRITEDelete an ingest endpoint. via DELETE /ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}
svix_get_api_v1_appREADList of all the organization's applications. via GET /api/v1/app
svix_get_api_v1_app_by_app_idREADGet an application. via GET /api/v1/app/{app_id}
svix_get_api_v1_app_by_app_id_attempt_endpoint_by_endpoint_idREADList attempts by endpoint id Note that by default this endpoint is limited to retrieving 90 days' worth of data relative to now or, if an iterator is provided, 90 days before/after the time indicated by the iterator ID. If you require data beyond those time ranges, you will need to explicitly set the `before` or `after` parameter as appropriate. via GET /api/v1/app/{app_id}/attempt/endpoint/{endpoint_id}
svix_get_api_v1_app_by_app_id_attempt_msg_by_msg_idREADList attempts by message ID. Note that by default this endpoint is limited to retrieving 90 days' worth of data relative to now or, if an iterator is provided, 90 days before/after the time indicated by the iterator ID. If you require data beyond those time ranges, you will need to explicitly set the `before` or `after` parameter as appropriate. via GET /api/v1/app/{app_id}/attempt/msg/{msg_id}
svix_get_api_v1_app_by_app_id_destinationREADList of all the application's destinations. via GET /api/v1/app/{app_id}/destination
svix_get_api_v1_app_by_app_id_destination_by_destination_idREADGet a destination by id or uid. via GET /api/v1/app/{app_id}/destination/{destination_id}
svix_get_api_v1_app_by_app_id_destination_by_destination_id_transformationREADGet the transformation code associated with this destination. via GET /api/v1/app/{app_id}/destination/{destination_id}/transformation
svix_get_api_v1_app_by_app_id_endpointREADList the application's endpoints. via GET /api/v1/app/{app_id}/endpoint
svix_get_api_v1_app_by_app_id_endpoint_by_endpoint_idREADGet an endpoint. via GET /api/v1/app/{app_id}/endpoint/{endpoint_id}
svix_get_api_v1_app_by_app_id_endpoint_by_endpoint_id_headersREADGet the additional headers to be sent with the webhook. via GET /api/v1/app/{app_id}/endpoint/{endpoint_id}/headers
svix_get_api_v1_app_by_app_id_endpoint_by_endpoint_id_msgREADList messages for a particular endpoint. Additionally includes metadata about the latest message attempt. The `before` parameter lets you filter all items created before a certain date and is ignored if an iterator is passed. Note that by default this endpoint is limited to retrieving 90 days' worth of data relative to now or, if an iterator is provided, 90 days before/after the time indicated by the iterator ID. If you require data beyond those time ranges, you will need to explicitly set the `before` or `after` parameter as appropriate. via GET /api/v1/app/{app_id}/endpoint/{endpoint_id}/msg
svix_get_api_v1_app_by_app_id_endpoint_by_endpoint_id_secretREADGet the endpoint's signing secret. This is used to verify the authenticity of the webhook. For more information please refer to the consuming webhooks docs. via GET /api/v1/app/{app_id}/endpoint/{endpoint_id}/secret
svix_get_api_v1_app_by_app_id_endpoint_by_endpoint_id_statsREADGet basic statistics for the endpoint. via GET /api/v1/app/{app_id}/endpoint/{endpoint_id}/stats
svix_get_api_v1_app_by_app_id_endpoint_by_endpoint_id_transformationREADGet the transformation code associated with this endpoint. via GET /api/v1/app/{app_id}/endpoint/{endpoint_id}/transformation
svix_get_api_v1_app_by_app_id_integrationREADList the application's integrations. via GET /api/v1/app/{app_id}/integration
svix_get_api_v1_app_by_app_id_integration_by_integ_idREADGet an integration. via GET /api/v1/app/{app_id}/integration/{integ_id}
svix_get_api_v1_app_by_app_id_msgREADList all of the application's messages. The `before` and `after` parameters let you filter all items created before or after a certain date. These can be used alongside an iterator to paginate over results within a certain window. Note that by default this endpoint is limited to retrieving 90 days' worth of data relative to now or, if an iterator is provided, 90 days before/after the time indicated by the iterator ID. If you require data beyond those time ranges, you will need to explicitly set the `before` or `after` parameter as appropriate. via GET /api/v1/app/{app_id}/msg
svix_get_api_v1_app_by_app_id_msg_by_msg_idREADGet a message by its ID or eventID. via GET /api/v1/app/{app_id}/msg/{msg_id}
svix_get_api_v1_app_by_app_id_msg_by_msg_id_attempt_by_attempt_idREAD`msg_id`: Use a message id or a message `eventId` via GET /api/v1/app/{app_id}/msg/{msg_id}/attempt/{attempt_id}
svix_get_api_v1_app_by_app_id_msg_by_msg_id_endpointREADList endpoints attempted by a given message. Additionally includes metadata about the latest message attempt. By default, endpoints are listed in ascending order by ID. via GET /api/v1/app/{app_id}/msg/{msg_id}/endpoint
svix_get_api_v1_app_by_app_id_poller_by_sink_idREADReads the stream of created messages for an application, filtered on the Sink's event types and Channels. Plan: polling endpoints are an Enterprise feature (svix.com/pricing, fetched 2026-09-13). via GET /api/v1/app/{app_id}/poller/{sink_id}
svix_get_api_v1_app_by_app_id_poller_by_sink_id_consumer_by_consumer_idREADReads the stream of created messages for an application, filtered on the Sink's event types and Channels, using server-managed iterator tracking. Plan: polling endpoints are an Enterprise feature (svix.com/pricing, fetched 2026-09-13). via GET /api/v1/app/{app_id}/poller/{sink_id}/consumer/{consumer_id}
svix_get_api_v1_auth_stream_by_stream_id_sink_by_sink_id_poller_tokenREADGet the current auth token for the stream poller. via GET /api/v1/auth/stream/{stream_id}/sink/{sink_id}/poller/token
svix_get_api_v1_background_taskREADList background tasks executed in the past 90 days. via GET /api/v1/background-task
svix_get_api_v1_background_task_by_task_idREADGet a background task by ID. via GET /api/v1/background-task/{task_id}
svix_get_api_v1_connectorREADList all connectors for an application. via GET /api/v1/connector
svix_get_api_v1_connector_by_connector_idREADGet a connector. via GET /api/v1/connector/{connector_id}
svix_get_api_v1_event_typeREADReturn the list of event types. via GET /api/v1/event-type
svix_get_api_v1_event_type_by_event_type_nameREADGet an event type. via GET /api/v1/event-type/{event_type_name}
svix_get_api_v1_healthREADVerify the API server is up and running. via GET /api/v1/health
svix_get_api_v1_operational_webhook_endpointREADList operational webhook endpoints. via GET /api/v1/operational-webhook/endpoint
svix_get_api_v1_operational_webhook_endpoint_by_endpoint_idREADGet an operational webhook endpoint. via GET /api/v1/operational-webhook/endpoint/{endpoint_id}
svix_get_api_v1_operational_webhook_endpoint_by_endpoint_id_headersREADGet the additional headers to be sent with the operational webhook. via GET /api/v1/operational-webhook/endpoint/{endpoint_id}/headers
svix_get_api_v1_operational_webhook_endpoint_by_endpoint_id_secretREADGet an operational webhook endpoint's signing secret. This is used to verify the authenticity of the webhook. For more information please refer to the consuming webhooks docs. via GET /api/v1/operational-webhook/endpoint/{endpoint_id}/secret
svix_get_api_v1_streamREADList of all the organization's streams. via GET /api/v1/stream
svix_get_api_v1_stream_by_stream_idREADGet a stream by id or uid. via GET /api/v1/stream/{stream_id}
svix_get_api_v1_stream_by_stream_id_sinkREADList of all the stream's sinks. via GET /api/v1/stream/{stream_id}/sink
svix_get_api_v1_stream_by_stream_id_sink_by_sink_idREADGet a sink by id or uid. via GET /api/v1/stream/{stream_id}/sink/{sink_id}
svix_get_api_v1_stream_by_stream_id_sink_by_sink_id_eventsREADIterate over a stream of events. The sink must be of type `poller` to use the poller endpoint. via GET /api/v1/stream/{stream_id}/sink/{sink_id}/events
svix_get_api_v1_stream_by_stream_id_sink_by_sink_id_headersREADGet the HTTP sink headers. Only valid for `http` or `otelTracing` sinks. via GET /api/v1/stream/{stream_id}/sink/{sink_id}/headers
svix_get_api_v1_stream_by_stream_id_sink_by_sink_id_secretREADGet the sink's signing secret (only supported for http sinks) This is used to verify the authenticity of the delivery. For more information please refer to the consuming webhooks docs. via GET /api/v1/stream/{stream_id}/sink/{sink_id}/secret
svix_get_api_v1_stream_by_stream_id_sink_by_sink_id_transformationREADGet the transformation code associated with this sink. via GET /api/v1/stream/{stream_id}/sink/{sink_id}/transformation
svix_get_api_v1_stream_event_typeREADList of all the organization's event types for streaming. via GET /api/v1/stream/event-type
svix_get_api_v1_stream_event_type_by_nameREADGet an event type. via GET /api/v1/stream/event-type/{name}
svix_get_ingest_api_v1_sourceREADList of all the organization's Ingest Sources. via GET /ingest/api/v1/source
svix_get_ingest_api_v1_source_by_source_idREADGet an Ingest Source by id or uid. via GET /ingest/api/v1/source/{source_id}
svix_get_ingest_api_v1_source_by_source_id_endpointREADList ingest endpoints. via GET /ingest/api/v1/source/{source_id}/endpoint
svix_get_ingest_api_v1_source_by_source_id_endpoint_by_endpoint_idREADGet an ingest endpoint. via GET /ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}
svix_get_ingest_api_v1_source_by_source_id_endpoint_by_endpoint_id_headersREADGet the additional headers to be sent with the ingest. via GET /ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}/headers
svix_get_ingest_api_v1_source_by_source_id_endpoint_by_endpoint_id_secretREADGet an ingest endpoint's signing secret. This is used to verify the authenticity of the webhook. For more information please refer to the consuming webhooks docs. via GET /ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}/secret
svix_get_ingest_api_v1_source_by_source_id_endpoint_by_endpoint_id_transformationREADGet the transformation code associated with this ingest endpoint. via GET /ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}/transformation
svix_patch_api_v1_app_by_app_idWRITEPartially update an application. via PATCH /api/v1/app/{app_id}
svix_patch_api_v1_app_by_app_id_destination_by_destination_idWRITEPartially update a destination. Plan: polling, FIFO, message-broker and database destination types are Enterprise features (svix.com/pricing, fetched 2026-09-13); the error a lower plan receives is unmeasured. via PATCH /api/v1/app/{app_id}/destination/{destination_id}
svix_patch_api_v1_app_by_app_id_destination_by_destination_id_transformationWRITESet or unset the transformation code associated with this destination. via PATCH /api/v1/app/{app_id}/destination/{destination_id}/transformation
svix_patch_api_v1_app_by_app_id_endpoint_by_endpoint_idWRITEPartially update an endpoint. via PATCH /api/v1/app/{app_id}/endpoint/{endpoint_id}
svix_patch_api_v1_app_by_app_id_endpoint_by_endpoint_id_headersWRITEPartially set the additional headers to be sent with the webhook. via PATCH /api/v1/app/{app_id}/endpoint/{endpoint_id}/headers
svix_patch_api_v1_app_by_app_id_endpoint_by_endpoint_id_transformationWRITESet or unset the transformation code associated with this endpoint. via PATCH /api/v1/app/{app_id}/endpoint/{endpoint_id}/transformation
svix_patch_api_v1_connector_by_connector_idWRITEPartially update a connector. via PATCH /api/v1/connector/{connector_id}
svix_patch_api_v1_event_type_by_event_type_nameWRITEPartially update an event type. via PATCH /api/v1/event-type/{event_type_name}
svix_patch_api_v1_stream_by_stream_idWRITEPartially update a stream. via PATCH /api/v1/stream/{stream_id}
svix_patch_api_v1_stream_by_stream_id_sink_by_sink_idWRITEPartially update a sink. via PATCH /api/v1/stream/{stream_id}/sink/{sink_id}
svix_patch_api_v1_stream_by_stream_id_sink_by_sink_id_headersWRITEUpdates the Sink's headers. Only valid for `http` or `otelTracing` sinks. via PATCH /api/v1/stream/{stream_id}/sink/{sink_id}/headers
svix_patch_api_v1_stream_by_stream_id_sink_by_sink_id_transformationWRITESet or unset the transformation code associated with this sink. via PATCH /api/v1/stream/{stream_id}/sink/{sink_id}/transformation
svix_patch_api_v1_stream_event_type_by_nameWRITEPatch an event type for Streams. via PATCH /api/v1/stream/event-type/{name}
svix_patch_ingest_api_v1_source_by_source_id_endpoint_by_endpoint_id_transformationWRITESet or unset the transformation code associated with this ingest endpoint. via PATCH /ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}/transformation
svix_post_api_v1_appWRITECreate a new application. via POST /api/v1/app
svix_post_api_v1_app_by_app_id_autoconfigWRITECreate an AutoConfig subscription. via POST /api/v1/app/{app_id}/autoconfig
svix_post_api_v1_app_by_app_id_autoconfig_by_autoconfig_id_rotateWRITERotate the auth token and signing secret for an AutoConfig subscription. via POST /api/v1/app/{app_id}/autoconfig/{autoconfig_id}/rotate
svix_post_api_v1_app_by_app_id_destinationWRITECreates a new destination. Plan: polling, FIFO, message-broker and database destination types are Enterprise features (svix.com/pricing, fetched 2026-09-13); the error a lower plan receives is unmeasured. via POST /api/v1/app/{app_id}/destination
svix_post_api_v1_app_by_app_id_endpointWRITECreate a new endpoint for the application. When `secret` is `null` the secret is automatically generated (recommended). via POST /api/v1/app/{app_id}/endpoint
svix_post_api_v1_app_by_app_id_endpoint_by_endpoint_id_bulk_replayWRITEBulk replay messages sent to the endpoint. Only messages that were created after `since` will be sent. This will replay both successful, and failed messages A completed task will return a payload like the following: { "id": "qtask_33qen93MNuelBAq1T9G7eHLJRsF", "status": "finished", "task": "endpoint.bulk-replay", "data": { "messagesSent": 2 } } via POST /api/v1/app/{app_id}/endpoint/{endpoint_id}/bulk-replay
svix_post_api_v1_app_by_app_id_endpoint_by_endpoint_id_recoverWRITEResend all failed messages since a given time. Messages that were sent successfully, even if failed initially, are not resent. A completed task will return a payload like the following: { "id": "qtask_33qen93MNuelBAq1T9G7eHLJRsF", "status": "finished", "task": "endpoint.recover", "data": { "messagesSent": 2 } } via POST /api/v1/app/{app_id}/endpoint/{endpoint_id}/recover
svix_post_api_v1_app_by_app_id_endpoint_by_endpoint_id_replay_missingWRITEReplays messages to the endpoint. Only messages that were created after `since` will be sent. Messages that were previously sent to the endpoint are not resent. A completed task will return a payload like the following: { "id": "qtask_33qen93MNuelBAq1T9G7eHLJRsF", "status": "finished", "task": "endpoint.replay", "data": { "messagesSent": 2 } } via POST /api/v1/app/{app_id}/endpoint/{endpoint_id}/replay-missing
svix_post_api_v1_app_by_app_id_endpoint_by_endpoint_id_secret_rotateWRITERotates the endpoint's signing secret. The previous secret will remain valid for the specified grace period (default 24 hours). via POST /api/v1/app/{app_id}/endpoint/{endpoint_id}/secret/rotate
svix_post_api_v1_app_by_app_id_endpoint_by_endpoint_id_send_exampleWRITESend an example message for an event. via POST /api/v1/app/{app_id}/endpoint/{endpoint_id}/send-example
svix_post_api_v1_app_by_app_id_integrationWRITECreate an integration. via POST /api/v1/app/{app_id}/integration
svix_post_api_v1_app_by_app_id_integration_by_integ_id_key_rotateWRITERotate the integration's key. The previous key will be immediately revoked. via POST /api/v1/app/{app_id}/integration/{integ_id}/key/rotate
svix_post_api_v1_app_by_app_id_msgWRITECreates a new message and dispatches it to all of the application's endpoints. The `eventId` is an optional custom unique ID. It's verified to be unique only up to a day, after that no verification will be made. If a message with the same `eventId` already exists for the application, a 409 conflict error will be returned. The `eventType` indicates the type and schema of the event. All messages of a certain `eventType` are expected to have the same schema. Endpoints can choose to only listen to specific event types. Messages can also have `channels`, which similar to event types let endpoints filter by them. Unlike event types, messages can have multiple channels, and channels don't imply a specific message content or schema. The `payload` property is the webhook's body (the actual webhook message). Svix supports payload sizes of up to 1MiB, though it's generally a good idea to keep webhook payloads small, probably no larger than 40kb. via POST /api/v1/app/{app_id}/msg
svix_post_api_v1_app_by_app_id_msg_bulk_expungeWRITEDelete the payloads from the given messages under the current application Useful in cases when a message was accidentally sent with sensitive content. A message can't be replayed or resent once its payload has been deleted (or has expired). via POST /api/v1/app/{app_id}/msg/bulk-expunge
svix_post_api_v1_app_by_app_id_msg_by_msg_id_endpoint_by_endpoint_id_resendWRITEResend a message to the specified endpoint. via POST /api/v1/app/{app_id}/msg/{msg_id}/endpoint/{endpoint_id}/resend
svix_post_api_v1_app_by_app_id_msg_expunge_all_contentsWRITEDelete all message payloads for the application. This operation is only available in the Enterprise plan. A completed task will return a payload like the following: { "id": "qtask_33qen93MNuelBAq1T9G7eHLJRsF", "status": "finished", "task": "application.purge_content", "data": { "messagesPurged": 150 } } via POST /api/v1/app/{app_id}/msg/expunge-all-contents
svix_post_api_v1_app_by_app_id_msg_precheck_activeWRITEA pre-check call for `message.create` that checks whether any active endpoints are listening to this message. Note: most people shouldn't be using this API. Svix doesn't bill you for messages not actually sent, so using this API doesn't save money. If unsure, please ask Svix support before using this API. via POST /api/v1/app/{app_id}/msg/precheck/active
svix_post_api_v1_app_by_app_id_poller_by_sink_id_consumer_by_consumer_id_seekWRITESets the starting offset for the consumer of a polling endpoint. Plan: polling endpoints are an Enterprise feature (svix.com/pricing, fetched 2026-09-13). via POST /api/v1/app/{app_id}/poller/{sink_id}/consumer/{consumer_id}/seek
svix_post_api_v1_auth_app_by_app_id_expire_allWRITEExpire all of the tokens associated with a specific application. via POST /api/v1/auth/app/{app_id}/expire-all
svix_post_api_v1_auth_app_portal_access_by_app_idWRITEUse this function to get magic links (and authentication codes) for connecting your users to the Consumer Application Portal. via POST /api/v1/auth/app-portal-access/{app_id}
svix_post_api_v1_auth_logoutWRITELogout an app token. Trying to log out other tokens will fail. via POST /api/v1/auth/logout. WITHHELD: Svix only lets that token log itself out, and this connection holds an environment API key (Svix answers 403), so this call is refused before any request is made.
svix_post_api_v1_auth_stream_by_stream_id_expire_allWRITEExpire all of the tokens associated with a specific stream. via POST /api/v1/auth/stream/{stream_id}/expire-all
svix_post_api_v1_auth_stream_by_stream_id_sink_by_sink_id_poller_token_rotateWRITECreate a new auth token for the stream poller API. via POST /api/v1/auth/stream/{stream_id}/sink/{sink_id}/poller/token/rotate
svix_post_api_v1_auth_stream_logoutWRITELogout a stream token. Trying to log out other tokens will fail. via POST /api/v1/auth/stream-logout. WITHHELD: Svix only lets that token log itself out, and this connection holds an environment API key (Svix answers 403), so this call is refused before any request is made.
svix_post_api_v1_auth_stream_portal_access_by_stream_idWRITEUse this function to get magic links (and authentication codes) for connecting your users to the Stream Consumer Portal. via POST /api/v1/auth/stream-portal-access/{stream_id}
svix_post_api_v1_connectorWRITECreate a new connector. via POST /api/v1/connector
svix_post_api_v1_environment_exportWRITEDownload a JSON file containing all org-settings and event types. Note that the schema for [`EnvironmentOut`] is subject to change. The fields herein are provided for convenience but should be treated as JSON blobs. via POST /api/v1/environment/export
svix_post_api_v1_environment_importWRITEImport a configuration into the active organization. It doesn't delete anything, only adds / updates what was passed to it. Note that the schema for [`EnvironmentIn`] is subject to change. The fields herein are provided for convenience but should be treated as JSON blobs. via POST /api/v1/environment/import
svix_post_api_v1_event_typeWRITECreate new or unarchive existing event type. Unarchiving an event type will allow endpoints to filter on it and messages to be sent with it. Endpoints filtering on the event type before archival will continue to filter on it. This operation does not preserve the description and schemas. via POST /api/v1/event-type
svix_post_api_v1_event_type_import_openapiWRITEGiven an OpenAPI spec, create new or update existing event types. If an existing `archived` event type is updated, it will be unarchived. The importer will convert all webhooks found in the either the `webhooks` or `x-webhooks` top-level. via POST /api/v1/event-type/import/openapi
svix_post_api_v1_operational_webhook_endpointWRITECreate an operational webhook endpoint. via POST /api/v1/operational-webhook/endpoint
svix_post_api_v1_operational_webhook_endpoint_by_endpoint_id_secret_rotateWRITERotates an operational webhook endpoint's signing secret. The previous secret will remain valid for the specified grace period (default 24 hours). via POST /api/v1/operational-webhook/endpoint/{endpoint_id}/secret/rotate
svix_post_api_v1_stats_usage_appWRITECreates a background task to calculate the number of message attempts (`messageDestinations`) made for all applications in the environment. Note that this endpoint is asynchronous. You will need to poll the `Get Background Task` endpoint to retrieve the results of the operation. The completed background task will return a payload like the following: { "id": "qtask_33qe39Stble9Rn3ZxFrqL5ZSsjT", "status": "finished", "task": "application.stats", "data": { "appStats": [ { "messageDestinations": 2, "appId": "app_33W1An2Zz5cO9SWbhHsYyDmVC6m", "appUid": null } ] } } via POST /api/v1/stats/usage/app
svix_post_api_v1_streamWRITECreates a new stream. via POST /api/v1/stream
svix_post_api_v1_stream_by_stream_id_eventsWRITECreates events on the Stream. via POST /api/v1/stream/{stream_id}/events
svix_post_api_v1_stream_by_stream_id_sinkWRITECreates a new sink. via POST /api/v1/stream/{stream_id}/sink
svix_post_api_v1_stream_by_stream_id_sink_by_sink_id_secret_rotateWRITERotates the signing secret (only supported for http sinks). via POST /api/v1/stream/{stream_id}/sink/{sink_id}/secret/rotate
svix_post_api_v1_stream_event_typeWRITECreate an event type for Streams. via POST /api/v1/stream/event-type
svix_post_ingest_api_v1_sourceWRITECreate Ingest Source. via POST /ingest/api/v1/source
svix_post_ingest_api_v1_source_by_source_id_dashboardWRITEGet access to the Ingest Source Consumer Portal. via POST /ingest/api/v1/source/{source_id}/dashboard
svix_post_ingest_api_v1_source_by_source_id_endpointWRITECreate an ingest endpoint. via POST /ingest/api/v1/source/{source_id}/endpoint
svix_post_ingest_api_v1_source_by_source_id_endpoint_by_endpoint_id_secret_rotateWRITERotates an ingest endpoint's signing secret. The previous secret will remain valid for the specified grace period (default 24 hours). via POST /ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}/secret/rotate
svix_post_ingest_api_v1_source_by_source_id_token_rotateWRITERotate the Ingest Source's Url Token. This will rotate the ingest source's token, which is used to construct the unique `ingestUrl` for the source. Previous tokens will remain valid for 48 hours after rotation. The token can be rotated a maximum of three times within the 48-hour period. via POST /ingest/api/v1/source/{source_id}/token/rotate
svix_put_api_v1_app_by_app_idWRITECreate or update an application. via PUT /api/v1/app/{app_id}
svix_put_api_v1_app_by_app_id_destination_by_destination_idWRITECreate or update a destination. Plan: polling, FIFO, message-broker and database destination types are Enterprise features (svix.com/pricing, fetched 2026-09-13); the error a lower plan receives is unmeasured. via PUT /api/v1/app/{app_id}/destination/{destination_id}
svix_put_api_v1_app_by_app_id_endpoint_by_endpoint_idWRITECreate or update an endpoint. via PUT /api/v1/app/{app_id}/endpoint/{endpoint_id}
svix_put_api_v1_app_by_app_id_endpoint_by_endpoint_id_headersWRITESet the additional headers to be sent with the webhook. via PUT /api/v1/app/{app_id}/endpoint/{endpoint_id}/headers
svix_put_api_v1_app_by_app_id_integration_by_integ_idWRITEUpdate an integration. via PUT /api/v1/app/{app_id}/integration/{integ_id}
svix_put_api_v1_connector_by_connector_idWRITECreate or update a connector. via PUT /api/v1/connector/{connector_id}
svix_put_api_v1_event_type_by_event_type_nameWRITECreate or update an event type. via PUT /api/v1/event-type/{event_type_name}
svix_put_api_v1_operational_webhook_endpoint_by_endpoint_idWRITECreate or update an operational webhook endpoint. via PUT /api/v1/operational-webhook/endpoint/{endpoint_id}
svix_put_api_v1_operational_webhook_endpoint_by_endpoint_id_headersWRITESet the additional headers to be sent with the operational webhook. via PUT /api/v1/operational-webhook/endpoint/{endpoint_id}/headers
svix_put_api_v1_stats_usage_event_typesWRITECreates a background task to calculate the listed event types for all apps in the organization. Note that this endpoint is asynchronous. You will need to poll the `Get Background Task` endpoint to retrieve the results of the operation. The completed background task will return a payload like the following: { "id": "qtask_33qe39Stble9Rn3ZxFrqL5ZSsjT", "status": "finished", "task": "event-type.aggregate", "data": { "event_types": [ { "appId": "app_33W1An2Zz5cO9SWbhHsYyDmVC6m", "explicitlySubscribedEventTypes": ["user.signup", "user.deleted"], "hasCatchAllEndpoint": false } ] } } via PUT /api/v1/stats/usage/event-types
svix_put_api_v1_stream_by_stream_idWRITECreate or update a stream. via PUT /api/v1/stream/{stream_id}
svix_put_api_v1_stream_by_stream_id_sink_by_sink_idWRITECreate or update a sink. via PUT /api/v1/stream/{stream_id}/sink/{sink_id}
svix_put_api_v1_stream_event_type_by_nameWRITECreate or update or create a event type for Streams. via PUT /api/v1/stream/event-type/{name}
svix_put_ingest_api_v1_source_by_source_idWRITECreate or update an Ingest Source. via PUT /ingest/api/v1/source/{source_id}
svix_put_ingest_api_v1_source_by_source_id_endpoint_by_endpoint_idWRITECreate or update an ingest endpoint. via PUT /ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}
svix_put_ingest_api_v1_source_by_source_id_endpoint_by_endpoint_id_headersWRITESet the additional headers to be sent to the endpoint. via PUT /ingest/api/v1/source/{source_id}/endpoint/{endpoint_id}/headers
Often connected alongside
Put Svix behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.