A reliable JsonCut integration keeps the editable source separate from large media files and long-running rendering. This guide walks through that boundary from a customer-facing perspective.
Choose the right source
Use a normal project when the workflow owns the whole creative structure. Use a template when the design is approved and the integration should only supply a small set of typed inputs.
Upload files before the render
Upload the image, audio or video through the public multipart media endpoint. Assign project or template retention when the asset belongs to a durable source, then use the returned jsoncut-media reference in layers and template inputs.
POST /api/v2/media
Content-Type: multipart/form-data
file=@./product-demo.mp4
retention=project
projectId={projectId}Treat rendering as an operation
The create-render request returns an operation. Poll its public status or configure a webhook, then consume the output URL only after the operation succeeds.