Connect LSF to your application while keeping control of the user interface, approvals and publishing workflow.
The steps below describe video-task integration. For other workflows, use the Seed Audio guide or Asset Library guide.
1. Prepare your server
Keep API keys server-side. Use the API base URL and exact model aliases supplied during onboarding.
2. Submit once and track the task
Use a stable client request ID for the same logical request. Store the public task ID. If polling is interrupted, resume GET for that task instead of creating another POST. For Production and LSF Flash Fast/Standard, an authorized replacement key for the same LSF tenant and account can retrieve the original task. Do not replay the old POST under a new key. See key rotation and task access.
Download the original file
After completed, Native Flash and supported Production and standalone-enhancement video outputs can be downloaded with authenticated GET /v1/videos/{task_id}/content. Native Flash and Production also return metadata.url; enhancement uses metadata.video_url. Keep API keys on your backend and never forward the LSF Bearer token to an external media URL.
If a transfer is interrupted, download the same task result again instead of creating another video. Verify that the complete file arrived before using it. Access is temporary; save completed media promptly. Resumable downloads are not guaranteed. Production downloads and output fields · Enhancement downloads and output fields
For Native Flash key allowance, replacement-key access and identical-request replay, use the Native Flash recovery rules.
3. Retrieve and deliver
Wait for a terminal state, read the documented result URL and copy the media to your storage promptly. Your application records task-to-content relationships and handles publishing.