Skip to main content
API & Webhooks are available for studios that need custom pipeline integration. Access requires a request so our team can confirm that the API supports your workflow.
Use the Renderjuice API when your software needs to start work or inspect job state. Use webhooks when Renderjuice should notify your software about an event. Most production integrations use both.

​
Good uses for the API

DCC tools

Upload a Blender project and submit it from an add-on, exporter, or studio launcher.

Pipeline orchestration

Start validation and rendering after upstream publishing or approval completes.

Batch submission

Create jobs for a shot list and track each Renderjuice job ID in the production database.

Monitoring and delivery

Read job status, show frame progress, and move completed outputs into the next pipeline stage.

​
Request model

Renderjuice uses a two-part ingest flow. Your integration sends the file to object storage through a presigned URL, then creates a Renderjuice job from the returned upload slug. The separation keeps large file bytes out of the Renderjuice API request path. The slug connects the uploaded object to job creation; the returned job id identifies all later work.

Upload and render a job

Follow the canonical request sequence with copyable curl commands, polling rules, status meanings, and download fields.

​
API and webhooks

The onRenderComplete webhook can reduce completion polling. Your webhook handler should still fetch the job, confirm completed status, and request fresh download URLs.

​
Integration boundaries

  • API keys carry administrator access to one workspace. Store them in a secrets manager and keep them out of client-side applications.
  • External API v1 accepts .blend and .zip sources smaller than 5 GiB through a single presigned PUT. It does not support multipart or resumable uploads. If this limit blocks your workflow, email support@renderjuice.com with the file sizes you need to upload. Your message helps us measure demand and prioritize multipart upload support.
  • Validation and rendering run in the background. Persist the job id and use GET /jobs/{id} as the state source.
  • The external API requires validation for each new job. It does not expose the dashboard’s previous-analysis reuse flow.
ZIP files created by Blend Project Packer can include project add-ons. Validation reads the pack manifest and lets the request select bundled add-ons by path.

​
Build the integration

API overview

Create an API key and learn which identifier belongs to each stage.

Endpoint reference

Inspect request fields, response schemas, and interactive examples.

Webhook events

Review supported event payloads and delivery behavior.

Related topics

Renderjuice API overviewChangelogOverviewUpload and render a jobWebhook Events