Documentation

Build personalized video workflows with BHuman.

Use these docs to create templates, map campaign data, personalize variables, add dynamic backgrounds, generate presenter videos, publish product updates, recover carts, and connect BHuman to your own tools.

System model

How BHuman works

  1. 01

    Create or import a source video

    Start in AI Studio with a recorded/uploaded presenter video, or generate the presenter, voice, and script in Speakeasy.
  2. 02

    Mark the parts that change

    Use variables for spoken text, URLs, background assets, CTA destinations, and other row-specific values.
  3. 03

    Connect data

    Send rows through CSV, Zapier, Pabbly, Leadr, or the API. Each row maps to the same template variables.
  4. 04

    Render and deliver assets

    BHuman renders asynchronously, then returns video status, share links, MP4 URLs, thumbnails, GIF previews, callback metadata, or product-specific publishing states.

Concepts

Terms used across the product and API

Template
The AI Studio source video that defines the presenter, script, transcript, voice behavior, and variables.
Variable
A personalized field such as a name, company, CTA URL, image URL, website URL, or background asset.
Campaign
A generation workflow that maps rows from CSV, Zapier, Pabbly, Leadr, or the API to a template.
Background segment
A timed section where BHuman places a website screenshot, LinkedIn capture, uploaded media, direct media URL, generic desktop, or keyed chroma scene behind the presenter.
Generated video
A render result with status, row index, share URL, MP4 URL, thumbnail, GIF preview, error message, and pipeline execution metadata when available.
Callback
A URL BHuman posts to after asynchronous rendering so your workflow can attach generated assets to a record.

Choose your path

Start with the workflow you are shipping

Browse

Browse by capability

AI Studio

Campaign features

Speakeasy

Leadr

Persona

Account settings

Developers

Reference

Developer reference

Use the docs pages for integration guidance and the live Swagger UI for exact endpoint schemas before launching production automation.

  • Use HTTPS callback URLs and allow repeated deliveries.
  • Store generated video IDs so callbacks and polling responses can be reconciled.
  • Keep variable names stable once a campaign, Zapier, Pabbly, or API workflow is live.