Start render
Start rendering a job.
Workflow
- Ensure job status is
validated(pollGET /jobs/{id}after starting validation) - Call this endpoint with your render configuration
- Poll
GET /jobs/{id}until status iscompleted - Retrieve outputs via
GET /jobs/{id}/downloads
Idempotency
This endpoint is idempotent for duplicate start requests. If a render was already started for the job, the API returns200 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
API key authentication. Format: Bearer RJ-XXX.... Get your API key from the Renderjuice dashboard.
Path Parameters
Unique identifier (UUID) of the job Unique identifier of the job
"123e4567-e89b-12d3-a456-426614174000"
Body
Configuration specifying how the job should be rendered, including output settings, frame ranges, and rendering options.
Response
Success
Unique identifier of the job
"123e4567-e89b-12d3-a456-426614174000"
Current status of the job
created, validating, validated, debugging, rendering, finalizing, completed, failed, canceled, booting, suspended "completed"
ID of the workspace this job belongs to
ISO 8601 timestamp when the job was created
ISO 8601 timestamp when the job was last updated
ID of the user who created the job
ID of the root folder containing the job files
Normalized rendering time in seconds (adjusted for GPU performance)
URL to a preview image of the rendered output, if available
Details about why the job failed, if applicable
Override configuration that was requested for this job
Final configuration that was used for rendering (may differ from requested)
Information about the job output files
Whether scene file analysis was skipped for this job
ID of the analysis associated with this job
Analysis results for the scene file
Information about the scene file used for rendering

