Skip to main content
Webhooks let Pureframe AI notify your server when a video finishes processing, a job fails, or your credit balance runs low. This removes the need to poll for these events.

Verifying webhook requests

Every delivery includes an X-Pureframe-Signature header. Verify it against the raw request body before trusting the payload. Python (Flask)
Node.js (Express)

Creating a webhook endpoint

The secret field is only returned once, at creation. Store it: you’ll need it to verify incoming deliveries. There is no way to retrieve it again; delete the endpoint and create a new one if you lose it.
The target URL must be publicly reachable: Pureframe AI rejects URLs pointing at private, loopback, or link-local addresses (e.g. 10.0.0.0/8, 127.0.0.1, 169.254.169.254) both when you register the endpoint and again at delivery time. Other endpoint operations:

Event types

Subscribe to only the events you need: deliveries for unsubscribed events are never sent to that endpoint.

Handling requests and failed deliveries

Every delivery is a POST with this envelope:
Return any 2xx status to acknowledge receipt. Check the endpoint’s delivery history for unsuccessful requests. You can manually redeliver a failed delivery by using the endpoint below.

Testing and signature verification

Fire a synthetic test event at any endpoint without waiting for a real one:
This delivers a webhook.ping event through the same signing and delivery path as real events, so it’s a reliable way to confirm your signature verification code works end to end. Inspect delivery history for an endpoint:
Manually redeliver a specific failed delivery instead of waiting for the automatic retry window:

Plan limits