AI avatar API for personalized videos of your own verified clone
The IdClone AI avatar API turns one approved video template into as many personalized videos as your product or CRM needs. You design the template once in the editor, mark the words that change (first name, company, product, meeting date), and your system sends the values. IdClone renders a video of your own verified clone saying the personalized script in their own voice and calls your webhook when the file is ready. The API is part of the Business and Enterprise plans.
What the API does and what it does not do
The API renders videos from templates that already exist in your workspace, presented by clones that already exist in your workspace. It does not create clones, it does not accept uploaded faces or voices, and it never renders a person who has not recorded their own consent. That boundary is deliberate. A developer can automate the words, but the identity behind the video always comes from a person who sat in front of their own camera, passed the live selfie check and spoke the one time consent phrase.
Fill template variables such as first name, company, role or product
Choose the clone, the language and the export resolution allowed by your plan
Receive a webhook with the status and a download link when the render finishes
Read the render status at any time by its identifier
How a request flows from your system to a finished video
First, a workspace editor builds a template in the script editor: the scenes, the framing, the brand kit, and variables written in double braces where personal details belong. A reviewer approves the template, which locks the fixed wording. Second, a workspace owner creates an API key for that workspace. Keys are issued per workspace, so an agency client workspace and an internal workspace never share credentials. Third, your system sends a render request with the template, the clone, the language and the variable values. IdClone checks that the clone belongs to the workspace and is active, fills the variables, estimates the length, and reserves the minutes from your plan. Fourth, when the video is rendered, IdClone posts the result to your webhook URL with the render identifier, the length in seconds and a link to the file.
A small illustrative request and response look like this.
When the render is done, the webhook body carries the same render identifier, the status "ready", the final length and the file link. A failed render reports the reason, and minutes reserved for it return to your plan.
POST /v1/renders
Authorization: Bearer <workspace api key>
Content-Type: application/json
{
"template": "tpl_followup_q4",
"clone": "cln_maria_sales",
"language": "en",
"variables": {"first_name": "Jordan", "company": "Northwind"},
"webhook_url": "https://your-app.example/hooks/idclone"
}
HTTP/1.1 202 Accepted
{
"render": "rnd_8f21c",
"status": "queued",
"estimated_seconds": 42
}How API renders count against your plan
API renders draw from the same monthly pool of avatar video minutes as videos made in the editor. Business includes 90 avatar video minutes and 300 voice clone minutes a month, at $499 a month or $249 a month billed yearly ($2,988). Enterprise includes 300 avatar video minutes and 700 voice clone minutes a month, at $1,499 a month or $749 a month billed yearly ($8,988), with higher rate limits for larger batches. Each personalized video counts its own length, so a 30 second follow-up sent to 100 leads uses 50 minutes. Translated versions count their length too. The usage page shows minutes used, minutes left and the date the pool renews, so you can size a campaign before you start it.
What teams build with the AI avatar API
Sales teams connect the API to a CRM step, so each new lead gets a short video from the rep who owns the account. Customer success teams send a welcome video that names the customer's company and the plan they bought. Product teams generate onboarding clips that mention the features a user switched on. Agencies run personalized campaigns for clients inside client workspaces, with each client's presenter recorded under their own consent. For the wider picture of where clone video fits, see the AI video generator for business overview.
Writing templates that sound natural when personalized
Keep the variable parts short and put them where a person would naturally say them, usually in the first sentence. Write the fixed part of the script for the ear, with short sentences and clear pauses. Add company and product names to the pronunciation dictionary so the clone says them the same way every time. Test the template with a few long and short values before you open it to a full list, because a 30 character company name changes the rhythm of a sentence. If you only need audio, the voice cloning module produces narration in the same voice and draws from voice clone minutes instead of video minutes.
Consent rules for API clones
Every clone used through the API belongs to a person in your workspace who recorded their own training footage and their own spoken consent from their own invite. An API key cannot attach a new face or voice, and it cannot render a clone from another workspace. Public figures and politicians are blocked from cloning altogether. Each export can carry a visible AI label and content credentials metadata, and every API render appears in the workspace audit log with the key that requested it. The full policy is on the consent and safety page.
Questions and answers
Which plans include the AI avatar API?
Business and Enterprise. Starter and Pro do not include API access. Enterprise has higher rate limits for large batches.
Can I create a clone through the API?
No. Clones are created only in the clone studio, by the person being cloned, after the live selfie check and spoken consent. The API renders videos with clones that already exist in your workspace.
How do I know when a video is ready?
Your webhook URL receives a message with the render identifier, status, length and file link. You can also read the status of any render by its identifier.
What happens if a render fails?
The webhook reports the failure and the reason, and the minutes reserved for that render return to your plan.
Can the API translate a template into other languages?
Yes. Pass the target language with the request. The translated version counts its length against video minutes like any other render, and we recommend reviewing the translated template in the editor once before running a batch.
Are API keys shared across workspaces?
No. Each key belongs to one workspace and can only use that workspace's templates and clones. Owners can revoke a key at any time.
Start building personalized video on Business
Create your account, record your clone, approve a template and send your first render from your own system.