Image and video production.Connected to your product.
Create projects, fill templates and render images or video from your own code. Requests return at once, renders run in the background, and a signed webhook tells your app when the file is ready.
One request in.One signed event back.
Submit a render with an idempotency key and get its ID right away. When it finishes, JsonCut posts a signed event to your endpoint, so nothing has to keep a connection open.
- Same key, same renderRepeating a request with the same idempotency key returns the existing render.
- Signed with HMAC SHA-256Verify the raw body, then deduplicate by event ID.
- Retries and replayFailed deliveries are retried up to six times; after that you can replay them.
curl -X POST "$JSONCUT_API/api/v2/projects/$PROJECT_ID/renders" \
-H "X-API-Key: $JSONCUT_API_KEY" \
-H "Idempotency-Key: product-launch-42" \
-H "Content-Type: application/json" \
-d '{
"kind": "video",
"format": "mp4"
}'{
"id": "render-27a1…:1:completed",
"type": "render.completed",
"createdAt": "2026-08-30T12:24:18Z",
"data": {
"renderId": "render-27a1…",
"status": "completed",
"phase": "finalizing",
"progress": 100,
"artifactCount": 1
}
}A small public API.Everything production needs.
Six groups of operations, each documented with parameters, schemas and responses in the interactive reference.
Projects
Create and update image or video projects that stay editable in Studio.
Projects in the quickstartMedia
Upload or import images, video, audio and fonts once, then reference them by ID.
Media docsTemplates
Read a template’s fields, then render a fixed version with new values.
Template docsRenders
Queue an image or video, read its state, cancel it or download the file.
Render lifecycleBulk renders
Send JSON or CSV rows; each row is checked and tracked on its own.
Bulk generationWebhooks
Receive signed completed, failed and cancelled events and replay a delivery.
Webhook docs
One lifecyclefor every render.
Project, template and bulk renders all become the same render resource, for images and video alike. Your code branches on five states.
Read the render lifecycle- queued
- Accepted, waiting for a renderer
- rendering
- Frames are being produced
- completed
- The file and its metadata are ready to download
- failed
- A readable reason, and whether a retry makes sense
- cancelled
- Stopped on request before it finished
Fits the stackyou already run.
Any HTTP client
Plain JSON over HTTPS with an X-API-Key header, from any language.
OpenAPI 3.1
A public OpenAPI file to generate a typed client or test calls in the playground.
API referencen8n and Make
Fill templates and start renders from a no-code workflow.
MCP for agents
Let Claude, ChatGPT or another client work in the same projects.
JsonCut MCP
From first callto a file in your app.
Create or select
Start an image or video project, or select a versioned template.
Attach media and data
Use multipart media uploads and typed inputs rather than embedding large files in every request.
Render and observe
Submit an output job, poll or receive a webhook, then retrieve the result.
Before you integrate.Questions about the API.
Is JSON still the creative document format?
No. You design in Studio or with the AI Director; JSON is only how the API sends and receives projects and template values.
Can I render without storing a project?
An inline rendering path exists for deliberate one-shot work, while iterative workflows should use projects.
Is there an SDK?
Not as a package yet. The API is plain JSON over HTTPS with a public OpenAPI file, so any HTTP client works or you generate a typed one. n8n and Make call it without code.