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.
This API documentation is currently a work in progress. Detailed endpoint and payload docs are coming soon as we finalize the updated schema.

​
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

​
Next steps

The remainder of the API Reference tab will cover:
  • Submitting jobs: payload schema, supported file types, and callbacks.
  • 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 [email protected]