Yahoo Japan Brand Panel video: 16:9, 200 MB, 5 to 60 seconds

Yahoo! JAPAN Ads help lists a 16:9 video of 5 to 60 seconds, up to 200 MB, as H.264 or H.265 in MP4 or MOV. With Sume you can request aspect_ratio: "16:9" on POST /v1/videos, reach 30 seconds in one job on some models, and stitch longer cuts with Timeline.

The reported spec

This comes from the Yahoo! JAPAN Ads help page, so confirm it against the current Yahoo Japan Ads requirements before you buy placement.

Hitting 16:9 and the duration

Sume lists the aspect ratios and durations each model supports in GET /v1/videos/models. Limits differ by model: seedance-2.5 accepts 4 to 30 seconds, wan-3.0 accepts 2 to 30 seconds, and every other catalog model tops out at 15 seconds. Gemini Omni Flash 1.1 supports 16:9 or 9:16 at 3 to 10 seconds.

A clip of 5 to 30 seconds therefore fits one job on seedance-2.5 or wan-3.0. A 45 or 60 second spot needs several clips joined, which is what Timeline 1.0 is for.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: brand-panel-001" \
  -d '{
    "model": "seedance-2.5",
    "prompt": "Widescreen product film, slow dolly across a tidy desk, natural light",
    "aspect_ratio": "16:9",
    "resolution": "1080p",
    "duration": 20
  }'

Stitching past one job

Timeline 1.0 takes one audio spine plus ordered video[] slots and returns one MP4. The audio length can be 1 to 1800 seconds and there can be up to 200 slots. Use POST /v1/timeline-1.0/plan first: it is unbilled and returns duration_seconds, so you can check you land between 5 and 60 seconds. Its default output is 1080 by 1920, which is portrait, so set output.width to 1920 and output.height to 1080 for a 16:9 cut.

Check the file before you upload

The sample above does not guarantee a 200 MB ceiling or a codec, because the Sume docs do not state the encoded bitrate or codec of generated MP4s. Run Video inspect on the finished file. It returns probe facts, so you can read duration and size-related details from the file itself, then compare them with the Yahoo Japan requirements. If it is too large, that is a signal to lower resolution and render again.