Rendofy Developer Examples

Rendofy is a webhook-native video rendering API for automation workflows. Send a structured JSON payload, then receive the completed MP4 URL at a callback endpoint you control.

This repository contains public integration examples and a tested n8n workflow. It does not contain the Rendofy service implementation, credentials, customer data, or deployment configuration.

How it works

1. Your application sends api_key, callback_url, and payload to Rendofy.
2. Rendofy responds immediately with status: "queued" and a job_id.
3. Rendofy POSTs a completion or failure object to callback_url.
4. On success, use video_url to download or forward the MP4.

your workflow → Rendofy render request → job acknowledgement
      ↑                                      ↓
      └──── completed callback + video_url ──┘

Quick start

Set a key and callback URL in your environment:

export RENDOFY_API_KEY="your_api_key"
export CALLBACK_URL="https://your-public-endpoint.example/rendofy-callback"

Run one of the examples:

bash examples/curl/render.sh
node examples/javascript/render.mjs
python3 examples/python/render.py

Your callback endpoint must accept an HTTPS POST from Rendofy. For local development, expose a temporary public endpoint through your preferred tunneling tool; never commit its URL or any credentials.

API contract

POST https://api.rendofy.com/webhook/render-intake
Content-Type: application/json

{
  "api_key": "YOUR_RENDOFY_API_KEY",
  "callback_url": "https://your-app.example/rendofy-callback",
  "payload": {
    "title": "Launch update",
    "subtitle": "Generated by a workflow"
  }
}

Immediate response:

{ "status": "queued", "job_id": "..." }

Completed callback:

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

Failed callback:

{ "status": "failed", "job_id": "...", "error": "..." }

Treat callback status as authoritative. The initial request only confirms that Rendofy accepted the job.

Examples and documentation

• API quickstart
• Webhook receiver example
• cURL example
• JavaScript example
• Python example
• RSS → Rendofy → Advanced Content Pipeline
• n8n workflow setup

n8n workflow

The included workflow adds RSS filtering, completed-item duplicate prevention, optional AI script enrichment, safe retry handling, and optional multi-platform publishing adapters around the Rendofy render path. It preserves the tested n8n 2.32.0 Wait-node callback normalization and contains no API key, publishing credential, or provider credential.

Capacity and retries

Rendofy plans are based on concurrent renders, not per-render metering. If all available render slots are in use, retry when capacity is available; do not assume excess requests are held in an automatic queue.

Learn more

• Rendofy
• Video rendering API
• JSON to video API
• n8n video rendering
• RSS-to-video n8n tutorial
• Flat-rate video rendering API

For API access or integration support, contact hello@rendofy.com.

License

MIT