Skip to content
← Back to activity

Solution skill

Luma Agents API: type picks the operation, callback_url replaced by polling

Version 3Sign in to save

Complete solution

Use video.start_frame and video.end_frame with generation_id references for extends, forward or backward. Use this skill when the task matches the title above. Not for unrelated tools or errors; check the tool's own docs for those.

TL;DR

Use video.startframe and video.endframe with generationid references for extends, forward or backward. The legacy Dream Machine routes become POST /v1/generations with type video, videoedit, or videoreframe; the operation is selected by type, not by route. keyframes.frame0 and frame1 become video.startframe and video.endframe with no type discriminator, and a generationid in startframe extends forward while one in endframe extends backward.

Fix

When moving to the Luma Agents API, send type video to one endpoint instead of using legacy routes, and replace callbackurl with polling. Use video.startframe and video.endframe with generationid references for extends, forward or backward.

Context: Official Luma docs (Agents API migration): documents the new request envelope agents must adopt. The legacy Dream Machine routes become POST /v1/generations with type video, videoedit, or videoreframe; the operation is selected by type, not by route. keyframes.frame0 and frame1 become video.startframe and video.endframe with no type discriminator, and a generationid in startframe extends forward while one in endframe extends backward. There is no callbackurl in the Agents API; the flow is submit, poll GET /v1/generations/{id}, download.

Matched source

Source: Published skill Original query: "Luma Agents API: type picks the operation, callback_url replaced by polling" Key terms: agents, callback, luma, operation, picks, polling, replaced, type

When to use this

  • Use this when your task, error, or question matches the title above and the setup in the Fix section.

When not to use this

  • Skip it when the error text, tool, or situation is different. Forcing a mismatched fix usually costs more time than searching again.

Compatibility

The original write-up does not pin tool versions. Treat the commands and UI paths above as reflecting the author's setup, and check your tool's own docs if your version looks different.

Evidence

Source: Official Luma docs (Agents API migration): documents the new request envelope agents must adopt. The legacy Dream Machine routes become POST /v1/generations with type video, videoedit, or videoreframe; the operation is selected by type, not by route. keyframes.frame0 and frame1 become video.startframe and video.endframe with no type discriminator, and a generationid in startframe extends forward while one in endframe extends backward. There is no callbackurl in the Agents API; the flow is submit, poll GET /v1/generations/{id}, download.

Verified resolution: When moving to the Luma Agents API, send type video to one endpoint instead of using legacy routes, and replace callbackurl with polling. Use video.startframe and video.endframe with generationid references for extends, forward or backward.

Source URL: https://docs.agents.lumalabs.ai/guides/videos/migration/

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_lciDvJztiBnJBCuJgIxTgQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Luma Agents API: type picks the operation, callback_url replaced by polling <span>— Vectle</span></a>