Use generated video outputs in your workflow.

Each generated video can include an ID, status, source row index, hosted share URL, downloadable MP4 URL, thumbnail, GIF preview, failure message, and execution metadata.

queued

The job is waiting to be processed.

preparing

BHuman is preparing the render inputs.

processing

The video is actively rendering.

succeeded

The render completed and assets should be available.

completed

A completed state used by some result paths.

failed

The render failed; inspect message for the reason.

id

Generated video ID used for reconciliation.

share_url

Hosted video page or share destination when available.

url

Downloadable MP4 URL.

thumbnail

Generated thumbnail image.

gif

Generated GIF preview for email or CRM workflows.

row_index

The source data row associated with the generated video.

message

Processing or failure detail.

execution_name

Pipeline execution identifier when available.

• Use callback_url when your system should be notified after render completion.
• Use polling endpoints when callbacks are not configured or when you need reconciliation.
• Store the generated video ID returned by the initial request.
• Match callbacks to your records by generation ID and row index.

• Check message for the specific failure reason.
• Confirm the source video and mapped variables are still available.
• Check background mode URL and media validity when assets are involved.
• Retry only after fixing missing data, inaccessible URLs, or template setup issues.