Personade API

The API is how you do that from somewhere else: a Clay table, your CRM, a script, or whatever already knows who you want to reach. Base URL:

https://app.personade.com/api/v1

The shape of an integration

A campaign is the unit of work: one recording, one audience, one set of links at the end. Almost every integration is the same five steps.

1. Find the recording you want to build on with GET /templates. You film and upload that in Personade itself, not through the API.
2. Start a campaign on it with POST /campaigns.
3. Add people with POST /campaigns/{id}/leads, one row at a time or a thousand at once. Nothing is charged yet.
4. Render a few and watch one, then charge for the rest: POST /campaigns/{id}/preview, then POST /campaigns/{id}/generate.
5. Collect the links with GET /campaigns/{id}/videos and send them yourself.

Two things worth knowing up front

You film in the browser, not through the API

There is no endpoint that uploads a recording or creates a voice. Both need a person: the voice clone is gated on a consent tick stamped with an IP address and the exact wording that was agreed to. That is a legal act, and an API key cannot perform it on someone's behalf. So the API builds on recordings that already exist.

Watch one before you send two hundred

The worst thing this product can do is not a failed render. It is a good one with a mispronounced name, going out to real prospects in your own face and voice. Preview is a separate call from generate for that reason.

We send nothing

Personade makes the videos and the pages. It never emails or messages anybody. You get a list of links and you send them from your own tool, with your own domain and your own reputation behind them.

Guides

ClayTurn an enriched table into a video for every row.

Start here