Redeliver a Sume job webhook: POST /v1/jobs/{id}/webhook/redeliver
Redeliver re-sends the real terminal event of a job with a fresh timestamp and signature, even after all 10 automatic attempts are used. Needs jobs:write.
POST /v1/jobs/{job_id}/webhook/redeliver with a key that has jobs:write re-POSTs the job's real terminal event (job.completed, job.failed or job.canceled) with a fresh timestamp and signature (read 2026-10-06 in the webhook docs).
When should I use it?
Use it when your receiver was down and Sume used its automatic attempts. It does not consume one of the 10, and it does not change the destination URL; a new URL means a new job.
curl -X POST "https://api.sume.com/v1/jobs/$JOB_ID/webhook/redeliver" \
-H "Authorization: Bearer $SUME_API_KEY"What should I do in practice?
Check the job's webhook delivery status before redelivering.
- Treat
job_idas the idempotency key; a redelivery can duplicate an event. - Redeliver is different from Send test.
- Format run redeliver is documented separately under run webhooks.
Sources
Related posts
More in Developers
- Redis sorted set scheduler for AI video job polling in Python
Keep video job ids in a Redis ZSET scored by next-poll time, claim due ids with ZREM so no two workers poll one job, reschedule by next_poll_after_seconds.
- Refuse an empty Sume API key or webhook secret: a fail-fast loader
An empty SUME_API_KEY or webhook secret fails late and confusingly. Load both at boot, reject empty or whitespace values, and never print them. Python, tested.
- Video fallback ladder: why reusing an Idempotency-Key returns 409
On Sume's video API a repeated Idempotency-Key with a different body is a 409. When you fall back from one model id to the next, derive a new key per id.
- Same Idempotency-Key, two Sume members: two jobs, not one
A Sume Idempotency-Key is unique per workspace and per key owner. Two members who send the same string get two jobs. Namespace your keys by what you generate.
Written by Sume