Per-request webhook_url in run-ffmpeg-command

[auiphc]

Problem

The webhook URL is configured globally in the dashboard, making it painful to switch between environments. Local dev typically uses a tunneled URL (ngrok, etc.) that's different from production — manually updating the dashboard every time is error-prone.

Proposed Solution

Add an optional webhook_url field to the run-ffmpeg-command request body:

{
  "input_files": { "in_1": "https://example.com/input.mp4" },
  "output_files": { "out_1": "output.gif" },
  "ffmpeg_command": "-i {{in_1}} {{out_1}}",
  "webhook_url": "https://my-ngrok-url.ngrok.io/webhooks/rendi"
}

Behavior:

• webhook_url provided → use it, ignore global setting
• webhook_url omitted → fall back to dashboard URL (existing behavior)

Webhook payload format stays identical — purely a routing change.

Why Not Alternatives?

• Separate projects per env → multiple API keys overhead
• Polling → defeats the purpose of webhooks

[peternaf]

@auiphc thanks for the feedback. Better webhook control and handling are on our roadmap and will be implemented quite soon. We will update via email and in the announcmenets here

[auiphc]

Thanks for the prompt response! Glad to hear it's coming soon. Do you have an estimated release date for this feature?

[peternaf]

Should be the coming month