GET /v1/videos to check for the completed video. In some environments, the video may be returned synchronously in the same response.
Endpoint
Authentication
Pass anall_access API key as a Bearer token in the Authorization header.
Your API key. Format:
Bearer <api_key>. Must have all_access permission — read-only keys cannot call this endpoint.Path parameters
The ID of the domain to generate a video for. The domain must belong to your account.
Request body
Natural language description of the demo to generate. Describe the user flow, feature, or scenario you want to showcase.
Font to use for captions and text overlays. Valid values:
"Inter", "OpenSans", "Playwrite", "Poppins", "Roboto".When
true, captions are added to the video.When
true, B-roll footage is included in the video.Background music track. Valid values:
"observer", "lawrence", "all_i_am", "lust", "denied_access", "75_and_lower". Omit to use no music.Voice model for narration. Valid values:
"ash", "onyx", "nova", "fable". Pass null to omit narration.Background style ID. Pass
null to use no custom background.List of recipient contacts used to personalize the video narration and on-screen text.
When
true, contacts with a valid email are emailed a link to the video after generation completes. Defaults to false.Response
Generation requests are almost always queued. The response shape depends on whether the job was queued or completed synchronously.Queued response
Synchronous response
Error responses
| Status | Description |
|---|---|
400 | The domain_id is not a valid number, or the request body failed validation. |
404 | No domain found with the given ID, or the domain belongs to a different account. |
Examples
Queued response
200
Synchronous response
200
