first_frame_url and last_frame_url on Video 1.0: deprecated names
Video 1.0 still reads first_frame_url and last_frame_url, but the docs prefer image_url and end_image_url. The rename map and one rule about the end frame.
Use image_url and end_image_url on Video 1.0: the docs mark first_frame_url and last_frame_url as deprecated names for the same frames. Old requests keep their shape, but new code should use the preferred names.
What is the rename map?
Each deprecated alias points to one current field.
| Deprecated | Preferred |
|---|---|
| first_frame_url | image_url |
| last_frame_url | end_image_url |
| duration_seconds | duration |
Is there a rule that links the two frames?
Yes. end_image_url requires image_url (or the deprecated first_frame_url), so an end frame alone is not a valid request.
What does a current request look like?
Only public HTTPS URLs are accepted.
curl -X POST https://api.sume.com/v1/video-1.0/generate \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: v1-i2v-001" \
-d '{"prompt":"Gentle camera drift; keep the product locked in frame","image_url":"https://example.com/first-frame.png","resolution":"1080p","duration":6,"aspect_ratio":"16:9"}'Will these names exist on /v1/videos?
No. That route uses frame_images with a frame_type; see the field map and the video docs.
What else is only on the legacy URL?
Video 1.0 does not accept a model body field, and accepts aspect_ratio values auto, adaptive, 21:9, 16:9, 4:3, 1:1, 3:4 and 9:16. Resolution is 720p by default, with 1080p also allowed.
Use public HTTPS media URLs only, and send an Idempotency-Key so a retry returns the original job.
Sources
Related posts
More in Developers
- Video 1.0 generate_audio: why the docs say to omit it
Sume's Auto family always generates audio for Video 1.0 requests, so the docs tell you to omit generate_audio. What the field does and where audio is optional.
- Video 1.0 metadata field: stored on the job, not sent upstream
The metadata object on a Video 1.0 request is stored on the job as caller metadata and is not sent to the provider. Use it to tag jobs; the limits it has.
- Video 1.0 reference_audio_urls: why audio alone is rejected
In Video 1.0, reference_audio_urls (1 to 3 URLs) requires at least one reference image or video. Field limits for images, videos and audio references.
- routing_preset kling or grok on Video 1.0: accepted, then ignored
Video 1.0 still accepts the retired routing_preset values cost, speed, quality, grok and kling, but all of them run through Auto. How to pick a family instead.
Written by Sume