Jobs and results

Sume jobs represent asynchronous work such as image generation, video generation, AI Ads videos, Face Swap, Reference Analysis, and asset ingest.

When to use jobs

Use jobs whenever a create endpoint returns before work is complete. The initial response should give you a job id or a list of job ids. Store that id, then poll status and fetch results.

List recent jobs

CLI:

Supported list filters are limit, cursor, type, and status.

Poll one job

CLI:

Polling guidance:

Status class	What to do
Queued/running/processing	Wait and poll again. Use longer intervals for video jobs.
Completed	Fetch the result.
Failed/canceled/expired	Stop polling and show the sanitized error/status.

Fetch results

CLI:

Result payloads vary by job type. They can include generated media, Reference Analysis output, provider-safe metadata, or Asset Library ingest references.

Inline wait with CLI

For short jobs, the CLI can create and wait in one command:

For longer jobs, avoid blocking the session:

Error handling

If a job fails, report:

• job id
• status
• sanitized error code/message if present
• request id if present

Do not print raw provider payloads, full signed/private URLs, or large transcript/media payloads into logs.