API & Webhooks are available for studios requiring custom pipeline integration. To ensure we support your specific workflow, access is currently request-only.
How webhooks work
When a render milestone happens, Renderjuice sends a signed payload to your endpoint. Your system can then react instantly—no polling required. For complete technical details including available events, payload schemas, setup instructions, and signature verification, see the Webhook Events reference.Use cases
Webhooks are ideal for reactive automation—letting Renderjuice notify you when something happens, rather than constantly checking status.Notifications & file management
Ideal for producers, coordinators, and teams that want status updates without babysitting the dashboard:- Notify humans – push Slack/Discord/email alerts when jobs succeed or fail.
- Auto-deliver outputs – move rendered frames to Google Drive, Dropbox, S3, or on-prem storage.
- Organize intelligently – rename files and drop them into project-specific folders on arrival.
- Track costs – log job duration and GPU minutes into spreadsheets or BI tools automatically.
Advanced pipeline automation
For Pipeline TDs and technical teams orchestrating multi-stage workflows:- Chain pipeline stages – kick off compositing, encoding, or QC scripts as soon as frames land.
- Smart retries – detect failure events and call the API to restart jobs with tweaked settings.
- Multi-stage orchestration – coordinate multiple Renderjuice jobs, farm nodes, or services from a single webhook entry point.
- Custom quality checks – run validation scripts (checksum, frame diffs, etc.) and branch outputs based on results.