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.
The Renderjuice API lets your tools upload Blender projects, submit render jobs, monitor their status, and retrieve their outputs. All endpoints use this base URL:

​
Generate an API key

  1. Sign in to Renderjuice and select the workspace that your integration will use.
  2. Open Profile & Settings → API Keys.
  3. Select Create API Key and give the key a descriptive label, such as render-bot.
  4. Copy the key and store it in a secrets manager. Renderjuice shows it once.
Each API key has full administrator access to its workspace. Limit who can read the key and rotate it when an integration no longer needs access.

​
Authenticate requests

Send the key in the Authorization header with every Renderjuice API request:

​
Understand the identifiers

Renderjuice separates file transfer from job orchestration. The upload and job endpoints return different identifiers because each one controls a different resource. POST /uploads does not create a job. Wait for the file upload to return a successful response, then pass the slug to POST /jobs. Use the returned job id for the rest of the workflow.

​
Submit your first render

Upload and render a job

Follow the complete upload, validation, render, polling, and download sequence with copyable requests.

​
Explore the API

Endpoint reference

Inspect request fields, response schemas, and interactive examples for each endpoint.

API integration guide

Decide where API-driven rendering fits into a studio pipeline.

Webhook events

Receive render completion events instead of relying on polling alone.
Contact support@renderjuice.com if you need API access or help mapping an existing pipeline to these endpoints.

Related topics

Overview: Blender Feature Support on RenderjuiceOverviewUpload and render a jobAPI integrationsVideo Outputs (MP4)