A webhook-first Shotstack alternative for JSON-to-MP4 workflows.

When this alternative fits

Shotstack-style workflows can be a good fit when you need a vendor-specific edit decision list or timeline contract. Rendofy takes a narrower, automation-oriented approach: send a clean JSON payload to the render intake endpoint, keep the returned job_id, and wait for the completed callback. It is not a claim that every vendor plan or workflow behaves identically; compare the current contracts before migrating.

Side-by-side integration model

Migration decisions should be based on your actual template and delivery requirements. Rendofy preserves the JSON → asynchronous render → callback model; it does not translate a third-party timeline schema automatically.

Minimal JSON intake

The request is a normal HTTPS POST. Keep the API key in your environment or secret manager and provide a public HTTPS callback URL for the completed result.

curl -X POST https://api.rendofy.com/webhook/render-intake \
  -H "Content-Type: application/json" \
  -d @- <<JSON
{
  "api_key": "$RENDOFY_API_KEY",
  "callback_url": "https://your-domain.example/rendofy/callback",
  "payload": {
    "quote": "Ship useful video automation.",
    "author": "Rendofy"
  }
}
JSON

Queued response

{
  "status": "queued",
  "job_id": "<job-id>"
}

Completed callback

{
  "status": "completed",
  "job_id": "<job-id>",
  "video_url": "https://storage.example/video.mp4"
}

Deploying the callback safely

Make the callback route public over HTTPS, validate the returned job_id, and treat video_url as the hand-off to your next approved step. In n8n, the verified node or a Wait node can resume the same execution. In a custom service, persist the job context before accepting the callback.

Integrate without rebuilding your stack

More context

See the video rendering API reference for lifecycle details, the flat-rate pricing guide for concurrency plans, or the tested RSS-to-video tutorial for a complete callback workflow.