Create with the AI music video API from prompts, audio, lyrics, and visual assets.
Skip queue, polling, storage, and webhook glue with one async video workflow API.
audio + images + prompt + lyrics
task_id
actionable storyboard
edit or select shots
hosted MP4
Use one AI music video API for music apps, artist platforms, creator tools, and campaigns.
Music Apps
Let listeners, artists, and fan communities create AI music videos from audio, lyrics, prompts, and references through one async task.
Useful inputs
What ships
Direct model APIs generate clips; Beat API adds the AI Music Video API and AI Workflow API layer for sync, task state, file delivery, and ecommerce reuse.
Music video workflows touch audio, lyrics, references, processing, billing, and delivery.
After generate
BeatAPI keeps inputs, execution details, files, delivery events, and support traces on one task record.
01
Capture context
Audio, lyrics, references, and task id stay together.
02
Track state
Internal processing states become product-ready task states.
03
Close the loop
Usage, delivery events, files, and failures stay explainable.
Risk
One task lifecycle
Model-specific job states stay behind queued, processing, succeeded, and failed states your product can use.
Risk
Inputs stay together
Audio, lyrics, prompts, visual references, task id, and output stay attached to the same workflow record.
Risk
Charge, settle, refund
Usage can be explained when a music video succeeds, fails, or never reaches a terminal state.
Risk
Request and execution traces
A task keeps request id, execution trail, status trail, video output, delivery event, and failure reason together.
Send audio, lyrics, prompt, and references; receive a task id; poll or subscribe for the generated video.
Submit music inputs once and receive a task id for polling or status events.
View docsevent
task.succeeded
accepted
workflow.ready
media.ready
POST /v1/music-video/tasks
server request contract
{ task_id: "tsk_9f2" }
{ status: "processing" }
{ output_url: "https://media.beatapi.io/outputs/task_xxx/0.mp4" }
sk_demo_8x92...k
server-side key active
1,240
usage
99.7%
events
The common feedback is about fewer custom scripts, clearer task states, and faster support handoffs.
Understand input limits, editable storyboards, single-shot revisions, selected-shot composition, task states, credit billing, file delivery, and support evidence.
Create an API key, submit audio, lyrics, prompts, and references, then track the task lifecycle.
Create API keyAn AI Music Video API turns audio, lyrics or SRT, prompts, and reference images into a video workflow your product can control. BeatAPI returns a task ID, exposes lifecycle and storyboard states, and delivers hosted shot media and a final MP4 URL.
Raw model APIs generate individual assets. BeatAPI adds the production workflow around them: validated inputs, unified task states, editable storyboard operations, persistent files, usage accounting, polling, webhooks, hosted outputs, and support-ready logs behind one API contract.
BeatAPI accepts a 10–180 second audio file and 1–7 public HTTPS reference images. Optional controls include prompts, lyrics or SRT, subtitles, lip sync, style, aspect ratio, 540p/720p/1080p resolution, quality, and automatic or manual composition. Upload local assets through /v1/files first.
Yes. Supported workflows return an ordered storyboard with stable shot IDs and shot metadata. You can retrieve or edit one shot, then compose only the selected shot IDs into a new MP4 without restarting the full task. Every operation stays linked to the original task ID.
Task creation returns a task ID. Poll GET /v1/tasks/{task_id} every 5–10 seconds as the source of truth, or add lifecycle webhooks. Statuses distinguish queued and processing work, storyboard review or action, editing, composition, success, and failure.
BeatAPI reserves or charges credits when generation or a storyboard operation is accepted, settles successful work, and refunds eligible failures. Cost depends on duration, resolution, quality, optional lip sync, and separate shot-edit or composition work. The credit ledger records charged, settled, and refunded usage.
BeatAPI keeps source inputs, uploaded files, storyboard shots, edit and composition operations, status history, credit events, execution logs, hosted outputs, webhook deliveries, request IDs, and failure reasons together. Developers and support teams get one traceable record from request to delivery.
BeatAPI's AI Ecommerce Video API turns product or lifestyle images, an offer brief, duration, aspect ratio, language, and creative direction into asynchronous short-form ad tasks. It reuses the same task, file, credit, webhook, and hosted-output layer as Music Video.
Read the developer Docs for endpoint guides, request and response schemas, workflow examples, credit rules, task states, and storyboard operations. Download /openapi.yaml for the importable API contract used by code generators, API clients, and testing tools.
