Use the JSON already flowing through your system.

1. Send one structured request

Call POST https://api.rendofy.com/webhook/render-intake with your API key, a callback URL, and the data you want rendered. The API returns a queued status and job ID straight away.

{
  "api_key": "YOUR_RENDOFY_API_KEY",
  "callback_url": "https://automation.example/callback",
  "payload": { "quote": "Ship the workflow, not a manual process.", "author": "Your team" }
}

Use representative field names and values from your system. Rendofy handles template-compatible payloads directly and can handle unmatched payloads as custom compositions.

2. Receive the MP4 at your callback URL

When rendering finishes, Rendofy posts a completion object to the callback URL. Use video_url in the next step of your integration. The callback-based model is designed for services where rendering should not block the caller.

{
  "status": "completed",
  "job_id": "...",
  "video_url": "https://...mp4"
}

3. Make the workflow resilient

Store the key as a secret, use a callback endpoint dedicated to the execution that requested the render, and treat the result as asynchronous. Plans cap simultaneous renders; when capacity is full, retry after a slot is free. Do not assume a request will wait in a queue.