Webhooks: subscribing to clip and render events

Webhooks push real-time events to your server when Choppity finishes work. They pair with the API for hands-off Content OS pipelines that react the moment a render completes.

Setup

Owners open Settings, add a webhook URL (HTTPS only), and select events such as clip job completed or render finished. Save the signing secret when shown because it is needed for verification.

Verify signatures

Each delivery includes a signature header. Validate it with your secret before trusting the body. Reject replayed or tampered payloads to keep automation trustworthy under attack.

Handle retries

Respond with HTTP 2xx quickly after enqueueing work. Failures retry with backoff. Process jobs idempotently because the same event may arrive twice during network blips.

Auth note

Webhook configuration uses Firebase JWT session auth in the app, not API keys. Use keys to call the API after you receive an event and need clip details.