Live sale replay: three highlight trims, keyframe then exact

To pull highlights from a live-sale replay, import the replay and send one Sume POST /v1/video-trim per moment, each with its own start and duration. The replay can be up to 1800 seconds, which is 30 minutes, and each cut can run from 0.2 up to 900 seconds. A cut costs $0.02, so three highlights cost $0.06.

The limits and the two precision modes are from Video trim (read 2026-10-06). Use keyframe for a fast first look, and exact for the cut you will publish.

What is the difference between keyframe and exact?

exact, the default, is a frame-accurate re-encode. keyframe is a stream copy that can start up to a keyframe interval early, so read actual_start_seconds in the result and re-base your times against it.

What do three highlight requests look like?

Send them as separate calls with a different Idempotency-Key each, since each is its own paid job. This one takes 20 seconds starting at 12 minutes into the replay:

curl -X POST https://api.sume.com/v1/video-trim \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: replay-highlight-1" \
  -d '{
    "video_url": "https://media.sume.com/artifacts/artf_demo/live-sale.mp4",
    "start": 720,
    "duration": 20,
    "precision": "keyframe"
  }'

What else should I do?

Judge the first look, then resend the winners with precision exact, and add output to conform them to 1080 by 1920. A replay over 30 minutes is refused with source_duration_exceeded.

• The source is not changed, and each result is a new MP4 with its own video_url.
• audio is keep by default, and drop removes it.
• A live clip with a person in it needs their permission to be reused as an ad, which is a call for your team, not for the API.