Daily fact or history channels
A topic list in a sheet, one call per row, one video and one Short per day in the same style.
Faceless video automation API
A faceless channel is a production line: pick a topic, write a script, record a voice, find visuals, edit, caption, cut a Short, upload. The Chitrio API runs that whole line from one request. You keep the part that needs judgement, choosing topics, in your own system (a spreadsheet, a database, a scheduler) and send each topic to POST /api/v1/videos. Chitrio returns a narrated video with moving scenes in a consistent look, captions burned in, music and an optional vertical Short, and can upload it to the workspace YouTube channel as private, unlisted or public. A signed webhook tells your system when each video is done so the next step of your pipeline can start.
Free trial to start · the cost is shown before every render
Straight answer: Automation does not remove responsibility. Review scripts for facts before publishing, and start with autoUploadPrivacy "private" so nothing goes public until you have checked it. Nobody can promise views; consistency and good topics are what help.
In the app, set the workspace voice, caption style and brand colour, and connect the YouTube channel if you want uploads.
For each topic send POST /api/v1/videos with the same visualStyle and tone, so every episode looks like the same channel.
On video.completed, download the files or let autoUpload publish them; on video.failed, log the reason and retry later.
Real endpoints and fields. The full reference, with Node.js and Python examples, is on the developers page.
Request: an episode that uploads privately
curl -X POST https://chitrio.com/api/v1/videos \
-H "X-Api-Key: YOUR_API_KEY" -H "Content-Type: application/json" \
-d '{"topic":"The lost city of Dwarka: what divers really found","durationInMinutes":4,"language":"en","tone":"documentary","visualStyle":"realistic","generateShort":true,"autoUpload":true,"autoUploadPrivacy":"private"}'Response
HTTP/1.1 202 Accepted
{ "jobId": "3f1c9a0e-...", "status": "Processing", "title": "The Lost City of Dwarka: What Divers Really Found" }Webhook your server receives
POST https://your-server.com/chitrio/webhook
X-Chitrio-Event: video.completed
X-Chitrio-Signature: t=1790791417,v1=ad4f3d52...
{ "event": "video.completed", "deliveryId": "5b0e1f2a...", "jobId": "3f1c9a0e-...",
"status": "Completed", "videoUrl": "https://chitrio.com/api/v1/videos/3f1c9a0e-.../download",
"shortUrl": "https://chitrio.com/api/v1/videos/3f1c9a0e-.../download?variant=short", "error": null }Named as they appear in the product, so you can find each one after you sign in.
An LMS, a CRM or an HR platform sends a topic and gets a finished video back.
Make a Short from one idea, or get a vertical Short and free Status cuts from every finished video.
A topic list in a sheet, one call per row, one video and one Short per day in the same style.
The same topic rendered in English and Hindi as two native videos for two channels.
Folk tales, mysteries and mythology in storybook, comic or stylised 3D looks with a storytelling tone.
One workspace and one key per client, so balances, voices and YouTube channels never mix.
No. Script, narration, visuals and captions are all produced for you. The voice is the one set in the workspace.
Yes, to the YouTube channel connected to the workspace, with autoUpload and a privacy of private, unlisted or public.
Send the same visualStyle and tone with every call; voice, captions and brand colour are workspace settings that every render follows.
Up to 3 per workspace at a time, and starting work is limited to 20 requests per 10 minutes per key. Queue the rest on your side.
Delivery is at least once with 3 retries over about 13 minutes, so deduplicate on deliveryId. The status endpoint always has the result.
Create a key, send one topic with autoUploadPrivacy private, and check the result before you scale.
Create a workspace and a key