Queues the same payload again as a new delivery with a new id, sent to the endpoint's current URL in case it was corrected since. A consumer that dedupes on the delivery id will therefore re-process it, which is the point.
The reply is the queued row, so status is pending and
deliveredAt is null; poll GET /webhooks/deliveries for the outcome.
Authorization
bearerAuth An API key created under Settings > API & Webhooks. Keys start with sf_live_.
In: header
Path Parameters
Response Body
application/json
application/json
application/json
curl -X POST "https://example.com/webhooks/deliveries/string/resend"{ "data": { "id": "dl9Zp1Ku6Lm4Wq8cx", "webhookId": "wh8Kd2mR5tQ9vN3xz", "event": "video.render_completed", "url": "https://hooks.example.com/shortfast", "status": "pending", "attempts": 0, "responseStatus": null, "lastError": null, "nextAttemptAt": "2026-08-06T11:14:00.000Z", "createdAt": "2026-08-06T11:14:00.000Z", "deliveredAt": null, "payload": { "event": "video.render_completed", "workspaceId": "k9WmT3xR2pQ7nV4bd", "createdAt": "2026-08-06T09:21:10.000Z", "data": { "video": { "id": "7bQxL2mF9dR4tK1sv", "title": "Why founders burn out" } } } }}List webhook endpoints GET
The webhook endpoints registered in this workspace, newest first. The signing secret is never included here: it is returned once, in the response that created the endpoint.
Send a test delivery POST
Fires a one-off signed test payload at the endpoint straight away, so you can check the URL and your signature verification before wiring up real events. Synchronous: the response reports the status your endpoint returned. It does not create a row in the delivery log.