Luma callback_url or polling: which Sume job mode matches
Luma's API docs list keyframes, loop and callback_url for ray-2. On Sume the equivalent choice is job mode: async, sync up to 30 s, subscribe or webhook.
If you used Luma's callback_url, the closest Sume setting is webhook mode on the job; if you polled Luma, use async and poll the job status. Luma's video generation docs list ray-2 and ray-flash-2, resolutions 540p, 720p, 1080p and 4K, keyframes, loop, concepts and callback_url. Sume's jobs expose four modes.
| Pattern | Luma API docs | Sume |
|---|---|---|
| Poll until done | Not covered by the page read | async mode: GET /v1/jobs/{id}/status then /result |
| Push on finish | callback_url | webhook mode |
| Wait inline | Not listed | sync mode, waits at most 30 s; subscribe is an alias of sync |
Choosing a mode
Video renders usually outlast the 30 second sync window, so sync suits short jobs and polling or webhooks suit the rest. Use webhook mode when a server can receive requests and you do not want a polling loop. Use async when the caller is a script or a laptop with no public address.
What to verify on a Sume webhook
Sume signs each delivery with HMAC SHA256 over <timestamp>.<raw_body>, sent as x-sume-webhook-signature: sume-v1=<hex>. Verify against the raw bytes, refuse to run with an empty secret, and expect redelivery: up to 10 attempts, 30 seconds apart, with a 10 second timeout on your endpoint. A redeliver endpoint exists for missed events. Details are on the webhooks page.
- Return a 2xx quickly and do the work after.
- Treat the same event arriving twice as normal.
- Keep a polling fallback for jobs with no event after your own timeout.
A caveat on the Luma side
Luma's public API docs list Ray 2, while the news page lists newer Ray3.2 and Ray3.14 releases. The docs may lag the product, so check which models your key can call before you map parameters.
Sources
Related posts
More in Developers
- Luma API callback_url vs Sume callback_url: signing and retries
Luma's video API takes a callback_url, and so does Sume's /v1/videos. What Sume's callback is signed with, how often it retries, and a Python verifier.
- Luma callback: 3 retries, 5 s timeout, vs Sume webhooks
Luma retries a failed callback at most 3 times with a 5-second timeout. Sume retries job webhooks up to 10 times with a 10-second timeout and signs each body.
- Lyria 3.5 is single-turn: budget retakes, not edits, on Sume
Google says Lyria 3.5 is single-turn and varies between calls. Plan retakes instead of edits: what 1, 3, 5 and 10 attempts cost on Google and on Sume.
- Lyria 3.5 section markers: how to write [0:00 - 0:10] Intro prompts
Lyria 3.5 accepts timestamped section markers like [0:00 - 0:10] Intro: in the prompt, written in the lyric language. Sume's router uses the same idea.
Written by Sume