role
From a real ticket: the customer ticked “omni reference” in their tool, but the request went to the generic video endpoint /v2/videos/generations, which only has images / videos arrays and no role. A single image is a first frame by rule, so adding a reference video got a 400 at submission. In the same request, the video was a path on the customer’s own machine that the provider could never reach.
The new FAQ explains why Seedance should always go through the native endpoint /seedance/api/v3/contents/generations/tasks, how to set role on each item, and how to pass reference videos (public URL or asset:// asset ID). See First Frame Mixed with Reference.
← Back to Live · 📚 Monthly archive