Render Farm API Documentation
Wire the render farm into your studio's own pipeline — submit jobs from a tool you wrote, trigger renders on approval, or pull finished frames into your asset manager. Tell us what you are building and we will send the developer documentation.
Who this is for
Studios and technical directors who would rather not open an application to send a render. If your pipeline already decides when a shot is ready, the render farm can be one more step in it — a submission fired by your own tool, a job triggered when a supervisor approves a take, or frames collected back into the asset manager without a person moving files.
If you only want to send scenes by hand, you do not need any of this. SkyRender Desktop already installs a submit button into Blender, Maya, 3ds Max, Cinema 4D and Unreal Engine, and the quick start guide covers the whole path from install to finished frames.
What to tell us
The more concrete the request, the shorter the conversation. Useful things to include: which application and version your pipeline is built around, whether you submit from an artist workstation or from a farm manager, roughly how many jobs a week you expect, and whether finished frames need to land somewhere specific. If your software is not on the supported list, say so here as well.
What happens next
The request is written to our support system before any email is sent, so a mail failure alone cannot lose it. You get a reference immediately, and a reply from a person rather than an automated document dump — what we send depends on what you are building.