Skip to main content
Webhooks are configured from the dashboard. Convertly sends JSON payloads to active endpoints whose event_types include the event, so your application can update records or notify users without polling every workflow.
Store the whsec_ secret when you create a webhook. Convertly uses it to sign each delivery.

What webhooks are for

Use webhooks to mark a user upload as ready, attach converted files to your own records, send a notification, or continue an automation after Convertly finishes the work.

Event envelope

Delivery headers

Verify signatures

The signature is an HMAC-SHA256 over {timestamp}.{rawBody} using the webhook secret.

Subscribable events

Convertly stores events before delivery and sends them asynchronously. Failed deliveries retry with exponential backoff for up to roughly seven days. A delivery that exhausts its attempts moves to the dead-letter state and can be replayed from Settings. After five consecutive dead-letter deliveries, Convertly automatically pauses the endpoint to protect both systems. Return any 2xx response promptly, verify signatures against the raw request body, and store convertly-event-id before applying side effects. Delivery is at least once, so consumers must be idempotent.
Last modified on July 28, 2026