An asynchronous API that fits automation
Video rendering takes longer than an ordinary HTTP request. Rendofy acknowledges a render request with a job ID, then sends the result to your callback endpoint when the MP4 is ready. That keeps n8n, Make, and custom services from having to poll a dashboard.
POST https://api.rendofy.com/webhook/render-intake
{
"api_key": "YOUR_RENDOFY_API_KEY",
"callback_url": "https://your-app.example/render-complete",
"payload": { "title": "A useful update", "subtitle": "From your workflow" }
}
→ { "status": "queued", "job_id": "..." }
(callback) → { "status": "completed", "job_id": "...", "video_url": "https://...mp4" }What the callback gives your workflow
On a completed render, the callback payload includes video_url. Your next step can download the MP4, store it in your own system, or pass it to another approved workflow action. A callback also means the original request does not need to hold an open connection while rendering occurs.
Capacity is explicit
Rendofy plans are based on concurrent renders, not per-render billing. Render volume is not metered monthly, but an account has a fixed number of simultaneous render slots. If all slots are busy, build a retry into your workflow rather than assuming requests are buffered indefinitely.