Sume webhook Send test vs Redeliver: they are not the same
Send test posts a dummy signed webhook.test payload to a URL you type. Redeliver re-sends a real job's terminal event. Pick the right one for the job.
Send test posts a dummy signed webhook.test payload to a URL you type and never replays a real job; Redeliver re-sends the real terminal event of one job (read 2026-10-06 in the webhook docs).
How do they differ?
The dummy body has no job_id, and Sume does not append it to Requests.
| Action | Sends | Needs |
|---|---|---|
| Send test | Dummy webhook.test | account:write |
| Redeliver | Real terminal event | jobs:write |
What should I do in practice?
Send test is also on /dashboard/webhooks.
- Use Send test to prove your verifier works.
- Use Redeliver to recover a missed result.
- Do not use one in place of the other.
Sources
Related posts
More in Developers
- Sume webhook signature header: why a sume-v2 entry is skipped
A Sume webhook verifier should compare only sume-v1= entries from the comma-separated header and skip other prefixes. Here is a Python check with a test.
- Sume webhook signature mismatch? Check the secret fingerprint header
Each Sume delivery carries x-sume-webhook-secret-fingerprint. Compare it with the dashboard before debugging code. Python verifier that refuses an empty secret.
- Sume webhook secret is per workspace: read it with account:read
Sume derives the webhook signing secret per workspace, not as a shared platform value. Read it on the dashboard or with GET /v1/webhooks/signing-secret.
- Sume webhook replay protection: reject timestamps over 5 minutes old
Reject Sume webhook callbacks whose timestamp is outside your tolerance window. The docs suggest five minutes. Redeliveries carry a fresh timestamp.
Written by Sume