Redeliver a webhook event
Replay a past delivery: the original payload is re-sent, byte for byte, to the
subscription's current URL. The original event ID is preserved so your endpoint can
dedupe, and the replay is recorded as a fresh attempt, so it shows up in
GET /v1/webhooks/logs next to the delivery it replays.
Both webhookId and eventId come from a row of GET /v1/webhooks/logs. Because
the stored payload is replayed as-is, a redelivery reflects the event as it was
emitted, not the current state of the resource.
Only deliveries inside the 30-day log retention window can be replayed; past that
the payload is gone and the request fails with a 500. Replays run the same
resource-group checks as live delivery, against both the key's groups and the
subscription's disabledResourceGroups.
API key authentication - use your Zernio API key as a Bearer token
In: header
ID of the webhook subscription that delivered the event
1 <= lengthStable event ID of the delivery to replay
1 <= lengthResponse Body
application/json
application/json
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.webhooks.redeliverWebhookEvent({ body: { webhookId: 'webhook_abc123', eventId: 'event_abc123', },});console.log(data);{
"success": true,
"message": "Webhook re-delivered"
}{
"error": "Unauthorized"
}{
"error": "This API key has the 'messages' resource group disabled. GET /api/v1/inbox/conversations requires it. Create a key with 'messages' enabled in the dashboard API keys tab.",
"code": "insufficient_permissions",
"required_group": "publishing"
}{
"success": true,
"message": "string"
}Delete webhook DELETE
Permanently delete a webhook configuration.
Send test webhook POST
Send a test webhook to verify your endpoint is configured correctly. The test payload includes event: "webhook.test" to distinguish it from real events. `webhook.test` belongs to the `webhooks` resource group, so a key with that group disabled is rejected with 403, as is a test fire on a subscription that lists `webhooks` in its own `disabledResourceGroups` (a 403, not a reported delivery failure). Replays of real events (redelivery, dead-letter requeue) run the same checks as live delivery, against both the key's groups and the subscription's.