Archive 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](#operation/create_event_type_api_v1_event_type__post).
If `expunge=true` is set then the event type is deleted instead of archived.
This can only be used in development environments.
Create 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.
Creates 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 any application in your environment, 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 ~350kb, though it's generally a good idea to keep webhook payloads small, probably no larger than 40kb.
The optional `application` property will be used to create an application if the application referenced in the path does not exist. If it does then this property is ignored.
Delete 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 expired.
DEPRECATED: Please use `app-portal-access` instead.
Use this function to get magic links (and authentication codes) for connecting your users to the Consumer Application Portal.
Get 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](https://docs.svix.com/consuming-webhooks/).
List 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.
DEPRECATED: please use list_attempts with endpoint_id as a query parameter instead.
List the message attempts for a particular endpoint.
Returning the endpoint.
The `before` parameter lets you filter all items created before a certain date and is ignored if an iterator is passed.
List all of the application's messages.
The `before` parameter lets you filter all items created before a certain date and is ignored if an iterator is passed.
The `after` parameter lets you filter all items created after a certain date and is ignored if an iterator is passed.
`before` and `after` cannot be used simultaneously.