Create one project from approved text
The example submits a brief and keeps its returned video ID with the source record.
Send an approved brief from your application to ngram, keep the returned video ID beside the customer record, and deliver the right version when it is ready. Use a preview for review or an MP4 when the destination needs a file.
The example submits a brief and keeps its returned video ID with the source record.
Use the job ID to inspect the current result and distinguish a preview from an MP4 ready for delivery.
Select a specific version and allowed resolution, then wait for the export URL before sending it onward.
Use an account-scoped key and a stable job reference so the result returns to the right caller.
Create a bearer key in Settings → API Keys and keep it on your server. Call GET /api/v1/account to check the linked account. API-key video creation requires Basic or a higher paid plan and available credits.
POST to /api/v1/videos:fromText for a text brief or /api/v1/videos:fromUrl for a public source URL. Use one Idempotency-Key for this logical request. Save the returned video ID with the record that started it.
GET /api/v1/videos/{id} returns the current status. A 202 create response means the job was accepted. For a job waiting on a plan or question, inspect state and pending before submitting another request.
For MP4 delivery, read the finished result URL. For a preview-first job, inspect live_preview or export the reviewed version with POST /api/v1/videos/{id}/exports. Check export status before forwarding a file.
Use these operations to keep the project linked to the record that requested it.
Create, rotate and revoke API keys in Settings. Keep a key on the server that owns the integration. Requests see the resources belonging to the connected ngram account.
Use the text route for approved copy and the URL route when a public page is the source. Choose MP4 delivery for a file or preview delivery for an editable review step.
Use the video ID from the create response. Check processing, completion or failure, and inspect any pending question when the request uses plan review.
Request an allowed resolution and include version_id when the file must match a reviewed cut. Poll the export until ready. A newer edit may require a new export.
Use a request from your server when the brief already lives in an application record. Choose chat for a brief that still needs discussion.
Create a customer update from the approved figures in your system. Store the source record and job ID together so the right editor can review the result.
Explore the workflowSubmit the approved release page when a shipped feature needs a short explanation. Check the result against the current product before giving it to customers.
Explore the workflowUse preview delivery when a person must inspect a version before receiving a file. Export the approved version only when the portal needs an MP4.
Explore the workflowThese features apply to the ngram project itself. Choose the relevant creation inputs and review the finished video before delivery.
Define the visuals the approved request needs before you create it.
Explore featureListen for phrases the narration must pronounce correctly before accepting the version.
See featureCheck script claims against the source bound to this project.
See featureMake a specific correction, then inspect the project’s newest version before export.
See featureUse an explanatory diagram when the source describes a process.
See featureInspect captions in the version the customer will receive.
See featureChoose a Brand Kit when creating a customer-facing project that needs its own identity.
See featureCreate a separate language version and keep its ID with the original customer record.
See featureChoose a source that contains the facts to explain. A text or URL creation request is useful when the input is already approved.
Use these Studio tools to prepare or revise the video when the job needs a creative change.
Assign the job to the team that can validate the source, check the correct customer destination and respond when the job needs attention.
Keep a sample request beside its expected response for developer onboarding.
Match the right customer record with its onboarding video.
Pick the starting surface and the result-handling mechanism independently. A request to create a video and a notification about its result do different jobs.
Receive completion and failure notifications after creating an API job.
Explore webhooksUse a compatible assistant for creative decisions and revisions in conversation.
Explore MCPStart and route a job through a managed workflow with supported trigger and action fields.
Explore ZapierUse the ngram node when a team already owns conditional routing and workflow operations in n8n.
Explore n8nPublic API Create and read | Webhooks Terminal notification | MCP Assistant | Zapier Workflow | |
|---|---|---|---|---|
| Who initiates | Your server | ngram on completion or failure | A person in chat | A trigger in a Zap |
| Result reference | Job and version IDs | Job and version IDs | Project or preview link | Mapped action result |
| Where it fits | Application-owned creation | Background notifications | A changing creative brief | Managed workflow routing |
| Next step | Store and review the result | Authenticate the event | Review in conversation | Continue the configured Zap |
FAQ
Still curious? Read the setup guide
Create a server-side key, check the account and keep the first video ID with its source record.