Update a webhook endpoint status.
Status transitions:
active: Re-enables the endpoint. Use this to:
paused: Pauses the endpoint. While paused:
active to resume and process queued notificationsarchived: Permanently archives the endpoint (soft delete)Note: The backing-off and disabled statuses are system-managed and cannot be set directly.
These occur automatically when delivery failures are detected. Use active to re-enable.
Authentication from public API requests
The desired status for the endpoint:
active: Enable/re-enable the endpointpaused: Pause the endpoint (notifications are queued)archived: Archive the endpoint (soft delete)active, paused, archived Optional reason for the status change (for audit purposes)
OK
The URL that will receive the webhook payload
The name of the webhook
The current status of the webhook endpoint:
active: The webhook is enabled and receiving events normally.paused: The webhook has been paused by the user. Events are queued and will be delivered when the endpoint is set back to active.backing-off: The system is temporarily backing off due to delivery failures. Delivery will be automatically retried at backingOffUntil. You can also immediately re-enable by setting status to active via the PATCH endpoint.disabled: The webhook has been automatically disabled due to repeated delivery failures. Re-enable by setting status to active via the PATCH endpoint.active, paused, backing-off, disabled When the endpoint was paused by the user (ISO 8601 timestamp)
When the system will automatically retry delivery (ISO 8601 timestamp). Only present when status is backing-off.
When the endpoint was automatically disabled due to repeated failures (ISO 8601 timestamp). Only present when status is disabled.