Skip to main content
POST
Start render
This is step 6 of the upload and render workflow. Call this endpoint after GET /jobs/{id} reports data.status: "validated". Poll that job endpoint until the status becomes completed, failed, or canceled.

How overrides work

Omit an optional field to use the value detected during validation. Renderjuice selects the supported Blender runtime, preserves the detected frame rate, and infers the Blender media type from outputFormat. Render jobs always produce image sequences. Legacy Blender movie formats are normalized to PNG frames. Set videoOutput: true to request an additional MP4 generated from PNG or JPEG frames; it does not enable direct Blender video rendering. Enum values are case-sensitive. Use the exact values listed in the request schema.

Example

Use analysis.output.sceneCameras[].objectName and analysis.output.viewLayers[].name from GET /jobs/{id} when selecting a camera or view layer.

Idempotency

This endpoint is idempotent for duplicate start requests. If a render was already started for the job, the API returns 200 OK with the current job payload and sets header X-Idempotent-Replay: true.
colorManagementPreset is required. Use default in most cases, or aces if your project uses ACES color management. All other fields are optional and will use values detected during validation.

Authorizations

Authorization
string
header
required

API key authentication. Format: Bearer RJ-XXX.... Get your API key from the Renderjuice dashboard.

Path Parameters

id
string<uuid>
required

Unique identifier (UUID) of the job Unique identifier of the job

Example:

"123e4567-e89b-12d3-a456-426614174000"

Body

application/json
requestedRenderConfig
object
required

Configuration specifying how the job should be rendered. Omitted optional fields use values detected during validation.

Response

Success

id
string<uuid>
required

Unique identifier of the job

Example:

"123e4567-e89b-12d3-a456-426614174000"

status
enum<string>
required

Current status of the job

Available options:
created,
validating,
validated,
debugging,
rendering,
finalizing,
completed,
failed,
canceled,
booting,
suspended
Example:

"completed"

userId
string<uuid>
required

Identifier of the user who created the job.

workspaceId
string<uuid>
required

Identifier of the workspace that owns the job.

createdAt
string<date-time>
required

ISO 8601 timestamp when the job was created

updatedAt
string<date-time>
required

ISO 8601 timestamp when the job was last updated

analysisId
string<uuid> | null

Opaque identifier of the associated analysis.

rootFolderId
string<uuid> | null

Identifier of the job input root folder.

normalizedSeconds
number

Normalized rendering time in seconds (adjusted for GPU performance)

previewUrl
string<uri> | null

URL to a preview image of the rendered output, if available

failedReason
object | null

Failure information intended for the client.

requestedConfig

Override configuration that was requested for this job

finalConfig
object | null

Final configuration that was used for rendering (may differ from requested)

output
object

Information about the job output files

isAnalysisSkipped
boolean

Whether scene file analysis was skipped for this job

projectId
string<uuid> | null

Project containing the job, when assigned.

uploadPreflight
object | null

Client-side ZIP inspection data captured before upload.

analysis
object | null

Client-visible validation state and scene metadata.

sceneFile
object

Client-visible scene file metadata.

{key}
unknown