401: Authentication Failed

Possible causes:

• X-API-Key is wrong or has extra whitespace.
• The key is disabled by an admin, or you disabled it yourself.
• The key is revoked.
• Global API key auth is turned off (API_KEY_AUTH_ENABLED=false).

Check the key status first, then create a new key if needed.

429: Too Many Requests

The default rate limit is 20 requests per minute. Read the Retry-After header and wait that many seconds. Use backoff in scripts; do not retry immediately.

400: Bad Request

The detail field explains the problem. Common causes:

• duration exceeds the maximum for the resolution.
• resolution is not 480p or 768p.
• Uploaded media format is not supported.
• size_bytes does not match the actual upload size.

409: Conflict

Usually means duplicate publish: one task can only be published once. Calling POST /api/v1/works again for the same task returns 409.

503: Service Not Configured

Common cases:

• Prompt optimization / tag generation: DASHSCOPE_API_KEY is missing.
• Reference media upload: R2 storage is not configured.

This is a platform configuration issue, not your parameters.

Failed Task

When a task fails, GET /api/v1/task/{task_id} returns an error field. Common causes:

• Not enough VRAM: lower resolution or duration.
• Node timeout: retry later.
• Reference media cannot be read: confirm the media is active.

If the error is unclear, send the task_id and error to an admin.