Public APIDeveloper integration

Create videos from your application.

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.

  • Create once — Send a brief or source URL with a stable request key.
  • Track the job — Read the current status, project link and available result.
  • Export a version — Request an MP4 for the version and resolution your account can deliver.

Three example API operations

Create one project from approved text

The example submits a brief and keeps its returned video ID with the source record.

Check what the job produced

Use the job ID to inspect the current result and distinguish a preview from an MP4 ready for delivery.

Export the reviewed version

Select a specific version and allowed resolution, then wait for the export URL before sending it onward.

How it works

From a request to a reviewed file

Use an account-scoped key and a stable job reference so the result returns to the right caller.

01

Check the account and key

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.

02

Submit an approved brief

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.

03

Inspect the existing job

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.

04

Deliver the intended version

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.

What the server exposes

Create, check and export through HTTP

Use these operations to keep the project linked to the record that requested it.

Account-scoped credentials

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.

Create from text or a URL

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.

Status and review

Use the video ID from the create response. Check processing, completion or failure, and inspect any pending question when the request uses plan review.

Version-specific export

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.

How it compares

Choose how your application starts and follows a job

Public API
Create and read
Webhooks
Terminal notification
MCP
Assistant
Zapier
Workflow
Who initiatesYour serverngram on completion or failureA person in chatA trigger in a Zap
Result referenceJob and version IDsJob and version IDsProject or preview linkMapped action result
Where it fitsApplication-owned creationBackground notificationsA changing creative briefManaged workflow routing
Next stepStore and review the resultAuthenticate the eventReview in conversationContinue the configured Zap

FAQ

Questions about the public video API

Key management is self-service for signed-in users. Video creation using an API key requires Basic or a higher paid plan, available credits and an allowed model. Check GET /api/v1/account and GET /api/v1/options before creating.

Still curious? Read the setup guide

Public API

Start with one approved request

Create a server-side key, check the account and keep the first video ID with its source record.