API & Webhooks are available for studios requiring custom pipeline integration. To ensure we support your specific workflow, access is currently request-only.
How it works
The API gives you programmatic access to Renderjuice. You make authenticated requests to manage jobs, check status, and retrieve results on your schedule.API workflow
When to use the API
Reach for the API when you need to control what happens on Renderjuice:Job management
- Submit renders from DCC tools – Blender addons, Maya scripts, or custom exporters can queue jobs without touching the dashboard.
- Bulk operations – submit hundreds of shots programmatically, retry failed jobs in batches, or adjust settings across a project.
- Status monitoring – build custom dashboards that poll job progress, aggregate metrics, or triage failures.
Multi-stage workflows
- Conditional rendering – submit jobs only if upstream validation passes, or fork different render settings based on asset metadata.
- Cross-system coordination – tie Renderjuice jobs to farm nodes, compositing stages, or delivery pipelines that need precise timing control.
Getting started
Ready to implement? See the API Reference for:- Authentication and API key setup
- Complete endpoint documentation
- Request/response schemas
- Interactive API playground
Best practices
- Authenticate securely – never hardcode API keys; use environment variables or secret managers.
- Handle rate limits gracefully – respect
429responses and implement exponential backoff. - Combine with webhooks – poll less frequently by relying on webhook notifications for completion events, then fetch details via the API only when needed.
- Validate inputs – check job payloads locally before submitting to catch errors early and reduce failed submissions.