callback_url for 30-second Seedance 2.5 and Wan 3.0 jobs

Add callback_url (it must be HTTPS) to the request and Sume POSTs to it when the job reaches a terminal state. The body is signed, with x-sume-webhook-timestamp and x-sume-webhook-signature headers, so verify before you trust it.

A 30-second render is the case where polling every 30 seconds adds up; a webhook replaces the loop.

Request

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "wan-3.0", "prompt": "Drone shot over a harbor at dawn",
       "duration": 30, "resolution": "480p",
       "callback_url": "https://example.com/hooks/sume"}'

What to handle

Notes

The webhook guide and the exact verification steps are in the API reference. Use the job status endpoint to double check any job you did not hear about.

Security basics

A webhook endpoint is public, so it needs verification. Compute the signature over the raw body, compare it in constant time, and reject requests with an old timestamp. Your verifier must refuse to run with an empty secret.

Respond quickly with a 2xx and do the heavy work (download, transcode) in a queue.

Webhook or poll

Use a webhook for production pipelines and polling for scripts and notebooks. Doing both is safe: the webhook triggers the next step and a slow poll catches anything missed.

Remember that polling at 30 seconds is the interval suggested in the docs.

• HTTPS only.
• Idempotent handlers.
• Log job ids.