Video API duration: whole seconds only, no 7.5 s clips

You cannot ask for a 7.5 second clip: duration on POST /v1/videos is an integer number of seconds, and every model's supported_durations lists whole seconds. Pick a value from that list for the model you use.

What does the duration field accept?

The request table types duration as an integer, described as the duration of the generated video in seconds. The model catalog field supported_durations is described as supported video lengths in whole seconds, so a fractional value has no listed meaning. The docs do not show a rounding rule, so send only whole numbers.

Which durations does each model list?

The ranges below come from the docs; every other catalog model tops out at 15 seconds. Always read GET /v1/videos/models for the live list rather than assuming one envelope.

How do I check a model before submitting?

Call the model list and read supported_durations for the id you plan to send. The docs advise checking resolutions, aspect ratios and durations before you submit a generation request.

curl "https://api.sume.com/v1/videos/models" \
  -H "Authorization: Bearer $SUME_API_KEY"

What if I need an in-between length?

Choose the nearest listed whole second and trim afterwards if you need less. Sume also ships a trim endpoint, described in the video trim docs if your pipeline needs an exact cut.

Does a longer clip change the flow?

Video generation is asynchronous: submit, receive a job id and polling URL, poll until completed, then download from the content URL. The docs suggest a polling interval of about 30 seconds and say generation typically takes 30 seconds to several minutes depending on the model and parameters.

Handle a failed status by reading the error field of the poll response.