Sume webhook Redeliver errors: 409 running or no URL, 403 jobs:write

POST /v1/jobs/{id}/webhook/redeliver returns 409 while the job runs or if it had no webhook_url, 403 without jobs:write, and 404 for a job you cannot see.

4 min readSume
All posts

POST /v1/jobs/{job_id}/webhook/redeliver re-sends a job's real terminal event, and it can answer four ways: 409 if the job is still running or was created without a webhook_url, 403 insufficient_scope if your key lacks jobs:write, 404 for a job you cannot see, and success otherwise. Each needs a different fix.

Reading each response

Redeliver responses (read 2026-10-06)
ResponseCauseFix
409Job still runningWait for a terminal state, then retry
409Created without a webhook_urlNothing to redeliver: poll the job instead
403 insufficient_scopeKey lacks jobs:writeUse a key with that scope (details.required_scope)
404A job you cannot seeUse the key of the member who created it
2xxSentDedupe on job_id at the receiver

The call

Redeliver does not change the destination URL, and it does not consume one of the automatic 10 attempts.

curl -X POST https://api.sume.com/v1/jobs/job_123/webhook/redeliver \
  -H "Authorization: Bearer $SUME_API_KEY"

A decision rule

Redeliver covers a callback that was lost. It is not a way to run a job again, and it is not a test button: Send test posts a dummy webhook.test payload to a URL you type.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume