Telegram sendLivePhoto: 10 s, 10 MB and trimming a clip

Telegram's sendLivePhoto needs a video no longer than 10 seconds and no larger than 10 MB, plus a static photo. Sume's video trim can cut a clip to 10 seconds and conform its width, height and fps, but it has no file-size target, so the 10 MB part is something you check on the result.

Telegram facts are from the Bot API page (Bot API 10.0, May 8, 2026 entry); Sume facts from Video trim. Read 2026-09-30.

What does sendLivePhoto require?

The live_photo parameter is the video: no longer than 10 seconds, not over 10 MB. Telegram recommends passing a file_id for a video already on its servers, or uploading with multipart/form-data. The page states that sending live photos by URL is currently unsupported, so download the Sume file and upload it.

How do I cut a clip to 10 seconds?

Import the clip to media.sume.com first, then call POST /v1/video-trim with start and duration. Exactly one of end or duration is allowed; duration runs from 0.2 to 900 seconds. An Idempotency-Key header is required.

curl -X POST https://api.sume.com/v1/video-trim \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: live-photo-trim-001" \
  -d '{
    "video_url": "https://media.sume.com/artifacts/artf_demo/talk.mp4",
    "start": 2,
    "duration": 10,
    "output": { "width": 720, "height": 1280, "fps": 30 }
  }'

How do I keep it under 10 MB?

Sume's docs offer no bitrate or byte-size field, and they refuse raw ffmpeg fields such as crf. The levers are shorter length and a smaller output frame size (256 to 2160 px) or lower fps (24, 25, 30 or 60), which require precision: "exact", the default. Then read the result and check the file size yourself before you upload.

What about the still photo?

sendLivePhoto also requires a photo. Sume's video frames extract stills at times you name. Other Telegram length rules are in video note limits.