Retry a failed 30-second video job on Sume without paying twice

Send the same Idempotency-Key when you retry a submit. Sume's docs say a replay returns the original job, so a timeout on the POST does not start a second 30-second render.

A job that ends failed is different: read the error field, fix the cause and submit a new request with a new key.

Which failures to retry

Example

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: ad-spot-0017" \
  -d '{"model": "wan-3.0", "prompt": "Ad spot, studio light", "duration": 30}'

Budget note

Sume reserves the price at submit. At 720p a 30-second Wan 3.0 job reserves about $3.75 and a Seedance 2.5 job about $17.33.

Job states to know

A job moves through pending, in_progress, then completed, failed or cancelled. Only the last three are terminal. Treat pending as normal for a while, because the docs say video generation can take from 30 seconds to several minutes.

On failure Sume reports the problem in the error field.

A safe retry loop

Retry network failures on the submit with the same key and a back-off. Do not loop on a failed job; fix it first. Cap the total attempts per creative.

Log the key, the job id and usage.cost so finance can reconcile.

• One key per creative.
• New key after a fix.
• Cap attempts per creative.