renders
Submit a render job
Enqueue a new render job on the GPU engine. The job moves through queued → processing → completed / failed asynchronously. Attach a webhook URL or register workspace-level webhooks to receive status updates. The response carries an ADVISORY ok + violations[] lint of the composition: the render is dispatched either way, and anything that actually blocks a submit is a 422 instead.
post/v1/renders
Request
- Base URL: https://api.framelane.io
- URL: https://api.framelane.io/v1/renders
- Auth: HTTP bearer
Headers
Idempotency-Keystring nullable
Request body
Response
Idempotent replay — same Idempotency-Key reused.
Example response
{
"id": "render_01J8QR2K5VKDGN2T4FBM3CZYX7",
"workspace_id": "ws_01J8QR2K5VKDGN2T4FBM3CZYX8",
"output": {
"url": "https://cdn-user.framelane.io/render_01J.../output.mp4",
"width": 1920,
"height": 1080,
"duration": 15.3,
"size_bytes": 12582912
},
"result": {
"language_code": "en",
"text": "Welcome back to the show."
},
"error": {
"message": "Source URL returned 404."
},
"metadata": {
"project_id": "proj_123",
"user_ref": "usr_abc"
},
"ok": true
}Changes
No recorded changes to this operation across all 1 revision of this API.