← All articles

CSV or API for Personalized Video: How to Choose

By BHuman Editorial TeamPublished

Compare BHuman’s spreadsheet and API workflows for personalized video. Use CSV for a hands-on batch; consider the API when your product or backend needs to control generation—subject to current beta access limits.

On this page5 sections

The quick decision

Choose CSV or Excel when you have a recipient list and want to test or run a manual batch. Consider the API when your product, CRM, backend, or form handler needs direct control over generation. If you need an automated trigger but not custom API control, BHuman also documents no-code and other integration paths.

BHuman Select data source dialog showing CSV or Excel and other campaign input choices
Choose where your campaign gets its recipient data. CSV or Excel is the file-upload option. Enlarge (opens in a new tab)

Choose CSV for a hands-on batch

CSV or Excel fits one-time lists, quick tests, and batch generation. Your spreadsheet headers become mapping options; upload the file, preview its rows, and map each template variable to a column. Use one column per variable, keep headers stable, and test a small file before uploading a full list.

For example, imagine a template with a first-name variable. A CSV column named first_name could hold each recipient’s replacement value. Send only the replacement text—not the fixed words already spoken in the template.

Consider the API for product-owned workflows

The API is intended for generation controlled by your product or backend. It sends recipient values to an existing AI Studio campaign; it does not create a Speakeasy presenter video from a prompt. Before making requests, you need an account, your own source video, a configured template and variables, and a campaign.

The documented campaign request uses an ordered variables array and a names matrix: each nested row supplies one recipient’s values in the same order. Generation runs asynchronously, so an accepted request means work is queued, not that the video is ready. You track results using returned generation IDs.

Check API access and operational limits first

The REST API remains in beta, and production credential provisioning is on hold pending qualification. Confirm your use case with support before production use; fresh-account access and several other parts of the integration are not fully qualified.

API generation uses account entitlements and video credits. There is no documented free API sandbox or separate API latency SLA. The API guide also warns that generation POST requests have no documented idempotency key: automatic retries can create additional work and charges. Start with one recipient, review the campaign’s estimated cost, and avoid blindly resubmitting if a request times out.

A practical choice checklist

Use these criteria to choose a starting point. If your process changes later, BHuman’s campaign workflow supports data-backed render jobs and can use different data sources.

  • Choose CSV or Excel for a manual batch, a one-time list, or a quick test.
  • Consider the API when your product or backend needs to control generation and you can handle credentials, asynchronous results, and access qualification.
  • Consider a documented no-code path when an app event should trigger generation without your own API integration.
  • Whichever route you use, map every required variable and make sure each row provides its value.