Webhooks
Update webhook
Update an existing webhook configuration (URL and/or events)
PATCH
Update webhook
Use this endpoint to update an existing webhook configuration. You can modify both the webhook URL and the events subscribed to.Documentation Index
Fetch the complete documentation index at: https://docs.sezzle.com/llms.txt
Use this file to discover all available pages before exploring further.
Valid Webhook Events
We accept the following Webhook events| Event | Trigger |
|---|---|
customer.tokenized | A customer is tokenized |
order.authorized | An order is authorized by Sezzle |
order.captured | An order is captured by Sezzle |
order.refunded | An order is refunded by Sezzle |
dispute.merchant_input_requested | A dispute is filed by a shopper and merchant input is required |
dispute.deadline_approaching | A dispute is moved to final notice by Sezzle |
dispute.closed.customer_win | The shopper wins the dispute and the order is refunded |
dispute.closed.merchant_win | The merchant wins the dispute and it is resolved in their favor |
dispute.closed.neutral | No clear winner is determined and the dispute is resolved neutrally |
Notes
- Both
urlandeventsfields are required in the request body - The webhook URL must be unique per merchant - you cannot update to a URL that is already in use by another webhook
- If the webhook UUID is not found, a 404 error will be returned
- Event subscriptions are replaced entirely - specify all events you want to receive, not just the changes
Authorizations
The authentication token generated from providing API Keys to Sezzle Gateway
Path Parameters
The webhook UUID to be updated
Body
application/json
The URL you are using to receive webhooks
An array of webhook events you wish to subscribe to
Available options:
customer.tokenized, order.authorized, order.captured, order.refunded, dispute.merchant_input_requested, dispute.deadline_approaching, dispute.closed.customer_win, dispute.closed.merchant_win, dispute.closed.neutral Update webhook