Webhooks API

What the webhooks endpoints are for

Manage the subscriptions that let you stop polling. Renders take minutes, and a webhook turns waiting into an event you receive rather than a loop you run.

Every delivery is signed, so a handler must verify the HMAC before trusting the body. Two endpoints exist specifically for the debugging you will otherwise do blind: POST /webhooks/{id}/test sends a signed ping from our servers so you can check your endpoint and your signature check without waiting for a real render, and GET /webhooks/{id}/deliveries returns the last 50 attempts when deliveries start failing.

The verification code and the retry schedule are on the webhooks guide.

curl -X POST https://app.makeaivideo.ai/api/v1/webhooks \
  -H "Authorization: Bearer $MAV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/hooks/makeaivideo",
    "events": ["video.ready"]
  }'

Webhooks API questions

How do I test a webhook without rendering a video?

POST /webhooks/{id}/test sends a signed test ping from our servers. The payload carries data.test = true, so a handler can tell it from a real event.

Why did my webhook stop receiving events?

Twenty consecutive delivery failures disable a subscription. Check GET /webhooks/{id}/deliveries for the failures, fix the endpoint, then re-enable it with PATCH is_active true.

How do I verify a webhook came from MakeAIVideo?

Compare the X-MakeAIVideo-Signature header against an HMAC-SHA256 of the raw request body keyed with your webhook secret, in constant time. Verify before parsing the JSON, because re-serialising a parsed object changes the bytes.