Skip to main content
We’ve updated video generation to use an asynchronous job-based Queue API. This change improves reliability, allows for better timeout handling, and provides visibility into job progress. The synchronous /v1/generate/ endpoints for video are now deprecated in favor of the new /v1/jobs/ endpoints.

What Changed

JavaScript SDK

The JavaScript SDK now uses client.queue instead of client.generate for video generation.

Before

After

For custom polling logic, you can manually control the submit/poll/result flow:

JavaScript Queue API Reference

Full documentation for the JavaScript Queue API

Python SDK

The Python SDK now uses client.queue instead of client.generate for video generation.

Before

After

For custom polling logic, you can manually control the submit/poll/result flow:

Python Queue API Reference

Full documentation for the Python Queue API

HTTP / REST API

The REST API now uses a three-step flow: submit, poll, and retrieve.

Before

After

Endpoint mapping

lucy-clip is now a previous-generation model. For new projects, use lucy-2.1 instead.

New endpoints for job management


Key Differences

Error handling

The Queue API provides more granular error information through job status:

Progress tracking

Monitor job progress with status callbacks:

FAQ

The old synchronous endpoints for video generation are deprecated. Image generation still uses /v1/generate/.
Yes, make sure you’re using the latest version of the SDK:
  • JavaScript: npm install @decartai/sdk@latest
  • Python: pip install decart --upgrade
Image generation continues to use the synchronous Process API (client.process in SDKs, /v1/generate/ for REST). Only video generation has moved to the Queue API.