Video 1.0 duration vs duration_seconds: what if they differ?
Video 1.0 accepts duration and its alias duration_seconds. If you send both they must agree; the value is checked against the Auto serving family.
On Video 1.0, duration_seconds is an alias of duration, and if you set both they must agree. Prefer duration; the value is an integer number of seconds validated against the Auto serving family.
What do the two fields mean?
The Video 1.0 table lists duration as integer seconds validated against the Auto serving family, and duration_seconds as its alias. It says to prefer duration.
What are the Auto limits?
The Video Router page says Auto create controls default to 720p and 8s, with 3 to 10 second clips at 16:9 or 9:16.
| Control | Value |
|---|---|
| Default resolution | 720p |
| Default duration | 8 s |
| Duration range | 3 to 10 s |
| Aspect ratios | 16:9 or 9:16 |
How do I avoid a conflict?
Send one field only. A body that sets duration: 6 and duration_seconds: 8 disagrees and is not valid.
curl -X POST https://api.sume.com/v1/video-1.0/generate \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: v1-dur-001" \
-d '{"prompt":"A quick product reveal on a white table","duration":6,"aspect_ratio":"9:16"}'What if I need more than 10 seconds?
Pin a model on /v1/videos: for example seedance-2.5 accepts 4 to 30 seconds. See the video docs.
Which other fields are validated the same way?
resolution is also validated against the Auto serving family, which supports 720p (the default when omitted) and 1080p from this legacy vocabulary. 4k is rejected on this URL.
Sources
Related posts
More in Developers
- Video 1.0 last frame: end_image_url needs image_url first
To set a last frame on Video 1.0, send end_image_url together with image_url. The docs list the modes: text, first frame, start and end frames, references.
- first_frame_url and last_frame_url on Video 1.0: deprecated names
Video 1.0 still reads first_frame_url and last_frame_url, but the docs prefer image_url and end_image_url. The rename map and one rule about the end frame.
- Video 1.0 generate_audio: why the docs say to omit it
Sume's Auto family always generates audio for Video 1.0 requests, so the docs tell you to omit generate_audio. What the field does and where audio is optional.
- Video 1.0 metadata field: stored on the job, not sent upstream
The metadata object on a Video 1.0 request is stored on the job as caller metadata and is not sent to the provider. Use it to tag jobs; the limits it has.
Written by Sume