Skip to main content
API & Webhooks are available for studios requiring custom pipeline integration. To ensure we support your specific workflow, access is currently request-only.
New to API workflow? Check out the API guide for use cases, workflow patterns, and best practices.
Renderjuice’s API exposes the same job ingestion, monitoring, and asset retrieval workflows available in the dashboard. Before calling any endpoint, you need an API key that is scoped to your workspace.

​
Generate an API key

  1. Sign in to the Renderjuice platform and make sure to be in the right workspace.
  2. Navigate to Profile & Settings → API Keys.
  3. Click Create API Key, give it a descriptive label (for example “render-bot”) and choose the appropriate permissions.
  4. Copy the key immediately—this is the only time it will be shown. Store it in a secrets manager; treat it like a password.
Every key inherits full admin privileges to the workspace, so issue keys sparingly and rotate them if an integration no longer needs access.

​
Authenticate requests

Include the key in the Authorization header using the Bearer scheme for every request: 
GET https://api.renderjuice.com/api/external/v1/jobs
Authorization: Bearer RJ-ABC-XYZ...
Accept: application/json

​
Upload-first workflow

Renderjuice’s API uses four steps for source-file ingestion:
  1. Request a presigned upload URL from Renderjuice.
  2. Upload a small .blend or .zip file directly to object storage with a single PUT.
  3. Create a job using the slug returned by the upload endpoint.
  4. Validate, render, and download outputs using the existing job endpoints.

​
Why upload comes first

POST /jobs turns an already-uploaded asset into a Renderjuice job. Create the job with the returned slug. You do not need to send the filename again.

​
Core request flow

Request an upload URL: 
POST https://api.renderjuice.com/api/external/v1/uploads
Authorization: Bearer RJ-ABC-XYZ...
Content-Type: application/json

{
  "fileName": "shot-010.zip",
  "fileType": "zip"
}
Receive an upload target: 
{
  "uploadUrl": "https://storage.example.com/...",
  "slug": "quiet-lake-1234",
  "expiresAt": "2026-03-26T13:00:00.000Z"
}
Create a job from the uploaded asset: 
POST https://api.renderjuice.com/api/external/v1/jobs
Authorization: Bearer RJ-ABC-XYZ...
Content-Type: application/json

{
  "slug": "quiet-lake-1234"
}

​
Current constraints

  • Small .blend and .zip uploads only
  • Single-request uploads via presigned URL
  • Presigned single-request uploads are limited to files smaller than 5 GiB
  • Multipart and resumable uploads are out of scope
  • Add-on uploads remain a separate workflow
See the API guide for the request and response shape, and the job lifecycle guide for the steps that follow job creation.

​
Next steps

The API Reference tab covers:
  • Requesting upload URLs and submitting jobs from uploaded assets.
  • Polling job status and retrieving outputs.
  • Monitoring job status and downloading outputs.
  • Handling webhooks, retries, and errors.
  • Rate limits, pagination, and other current constraints.
If you need access for your team or want to onboard to a private beta endpoint, reach out to support@renderjuice.com