Sora Videos API replacement: seconds and size on Sume

Rename seconds to duration (an integer), and replace size with resolution plus aspect_ratio. Sume's POST /v1/videos rejects size with 400 unsupported_parameter, so a Sora request body will not run unchanged.

OpenAI's deprecation page lists sora-2, sora-2-pro and dated snapshots with a 2026-09-24 shutdown and no recommended replacement. Its guide says no one-to-one replacement API is available. Sume facts are from Video generation; all pages read 2026-09-30.

How do the two request bodies map?

Why does size fail on Sume?

The docs say every v1 model reports supported_sizes: null, so size returns 400 unsupported_parameter. They tell you to use resolution and aspect_ratio, for example 720p with 16:9. Each model lists the resolutions it accepts in supported_resolutions.

What does the converted request look like?

Pick a model id from the catalog; seedance-2.5 is the docs' example.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: sora-port-001" \
  -d '{
    "model": "seedance-2.5",
    "prompt": "Slow dolly shot through a miniature paper city at blue hour",
    "duration": 8,
    "resolution": "720p",
    "aspect_ratio": "16:9"
  }'

Is a retry safe?

Send Idempotency-Key: a replay returns the original job instead of creating a second one. See the Sora shutdown migration guide for model-level alternatives.