POST /v1/videos { source, intent, voice }
API and SDK
Build video into your own product.
Create, manage, and ship videos programmatically with the Momo API and SDK from your own apps, products, and workflows.
201 Created → { id, status, share_url }
Video creation behind one API boundary
Create a job
Send source references, workflow intent, template, and delivery policy.
Track its lifecycle
Use status endpoints and webhooks instead of timing-sensitive polling.
Review or deliver
Embed the editor, request approval, or use the resulting hosted asset.
Ship it in product
Embed the player or editor and let your app own the experience.
What teams build on the API
Product integrations
Generate walkthroughs inside your own features.
Support agents
Let your bot answer with a rendered video.
Release automation
Create the launch video in the same pipeline as the release.
Customer portals
Serve personalized videos from your own app.
Typed requests
Build against explicit inputs, job states, errors, and output receipts.
Idempotent workflows
Safely retry creation requests without multiplying assets.
Other APIs return a file. Momo returns a governed asset.
Use the same Momo production system through an application boundary: typed jobs, explicit status and completion events, and workspace controls on every output.
FAQs
Does the API return a video immediately?+
Video creation is asynchronous. Jobs expose explicit status and completion events.
Can API outputs require review?+
Yes. Delivery policy can keep the output as a draft until an authorized reviewer approves it.