Programmatic rendering

Turn catalog data into render jobs.

Rendofy accepts structured JSON, acknowledges each job, then sends the completed MP4 URL to your HTTPS callback.

Batch from your source data

Use a catalog row, account record, or campaign entry to build one render request. Your scheduler controls how many jobs are in flight; the plan defines concurrent capacity, not a monthly render allowance.

Map a record

Prepare the values your composition needs, such as product name, offer, and image URL.

Submit JSON

POST the API key, callback URL, and render payload to the intake endpoint.

Handle the result

Use the callback's video_url in storage, review, or publishing steps.

Request and callback contract

The public intake accepts a JSON object with api_key, callback_url, and payload. Keep credentials in a secret store and send a callback URL reachable by Rendofy.

curl -X POST https://api.rendofy.com/webhook/render-intake \
  -H 'Content-Type: application/json' \
  -d "$(jq -n --arg key "$RENDOFY_API_KEY" --arg callback "$CALLBACK_URL" \
    '{api_key:$key,callback_url:$callback,payload:{quote:"SKU 104, ready to share",author:"Northstar Supply"}}')"

Accepted

HTTP 202
{"status":"queued","job_id":"…"}

Completed callback

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

Plan for capacity

Keep outstanding jobs within your concurrency limit. Do not assume excess requests are buffered automatically.

Compare by capacity, not monthly output

Metered APIs charge according to each provider's current per-render or credit rules. Rendofy plans use fixed monthly prices and concurrent-render limits: Starter is $39 for 2, Growth is $99 for 5, and Scale is $199 for 10. Each plan allows unlimited monthly render volume within its capacity and applicable fair-use rules.

Choose from measured peak overlap and output needs. A flat monthly plan does not mean unlimited simultaneous renders.

Compare Rendofy plans Workflow patterns