For the complete documentation index, see llms.txt. This page is also available as Markdown.

Create an Explainer Video

Produce your first AI-powered explainer video in just a few steps. This walkthrough uses the same /content/Create endpoint as podcasts, but switches the payload to outputType: "video" so the service renders motion visuals instead of audio-only narration. Video requests support three formats: explainer, brief, and cinematic.

Step 1: Create Content Request

Send a POST request to /content/Create with your preferred resources, set outputType to video, and optionally choose a format:

curl -X POST "https://api.autocontentapi.com/content/Create" \
  -H "accept: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "resources": [
      {
        "type": "website",
        "content": "https://example.com/article-about-ai"
      },
      {
        "type": "youtube", 
        "content": "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
      }
    ],
    "outputType": "video",
    "format": "explainer",
    "text": "Create an engaging explainer about current AI developments"
  }'

Example Response

Important: Save the request_id โ€” you'll use it to poll status and download the final video.

Choose a format

Explainer video requests use format to control the output. If you still send the generic duration parameter, it is ignored:

Format
Best for
Credits

explainer

Balanced default for most product, education, and marketing videos

50

brief

Tighter, punchier recaps and shorter social-friendly explainers

50

cinematic

Premium, more polished storytelling treatment

100

If you omit format, the API defaults to explainer. Use style separately when you want to change the visual aesthetic.

Optional: Guide titles, descriptions, and visuals

Use these fields to steer how the service names and presents the video:

Field
What it does

title

Sets an explicit video title. When present, this overrides the auto-generated title.

titlePrompt

Guides the model when auto-generating the title (e.g., ask for concise, listicle-style, or SEO-friendly phrasing).

descriptionPrompt

Steers the generated video description (tone, call-to-action, hashtags, etc.).

thumbnailImagePrompt

Directs the generated thumbnail artwork.

introImagePrompt

Directs the opening frame artwork.

Add any combination of these to the POST body:

Optional: Apply your brand via projects

If you have a saved project with brand assets, include the projects array (pass one or more IDs) to place your logo on the generated video and thumbnail:

See the brand logo recipe for more variations. Need a project first? Follow Create a Project (Brand Assets) to save a logo via imageUrl or imageData.

Step 2: Poll for Status

Use the request_id to check the processing status by calling /content/Status/{id}:

While Processing

Status Codes:

  • 0 = Pending (queued for processing)

  • 5 = Processing (generation in progress)

  • 100 = Completed (video ready!)

Step 3: Get Your Video

When status reaches 100, the payload includes a link to your generated video:

Titles or prompts you set in Step 1 flow into video_title, and image prompts steer image_url/thumbnail assets returned here.

๐ŸŽ‰ Success! Your explainer video is ready at the video_url, and you can grab the thumbnail from image_url.

Resource Types

You can mix and match resource types just like you would for a podcast:

Type
Description
Example

website

Any web page URL

"https://techcrunch.com/article"

youtube

YouTube video URL

"https://www.youtube.com/watch?v=VIDEO_ID"

text

Direct text content

"Your custom instructions or content"

pdf

PDF document URL

"https://example.com/document.pdf"

Need a specific payload? Check the new Explainer Video Scenario Examples for copy-paste curl requests covering languages, formats, styles, and every supported resource type.

Tips for Better Results

  1. Mix resource types โ€“ Combine websites, videos, and text for richer storytelling.

  2. Provide clear instructions โ€“ Use the text field to direct the pacing, tone, or call-to-action.

  3. Surface thumbnails โ€“ Store the image_url for embedding preview artwork alongside the finished video.

  4. Check status regularly โ€“ Processing typically takes 2-5 minutes for most requests; cinematic can take longer.

  5. Save the request_id โ€“ You'll need it to retrieve your video and any associated transcript.

Error Handling

If something goes wrong, the status response will include error details:

What's Next?

Last updated