Skip to main content
Diagram of Magica pushing webhook events to a customer server

Webhooks - Magica pushes events to your server

Webhooks let your server receive HTTP POST notifications for asynchronous model and workflow runs. Public REST consumers should verify the signature, respond quickly, and process events idempotently.
Delivery is powered by Svix: automatic retries, HMAC-SHA256 signatures, and delivery logging included.

Configure a webhook

Pass a webhook object when starting a model run or workflow run.
For standalone model runs, include the same webhook object in POST /v1/nodes/{nodeType}/run.

Supported events

Model runs and workflow runs support different event sets. When you omit events, Magica sends every event supported by that run type.

Event payload


Event types

run.started

A run begins executing.

run.completed

All requested work finished successfully.

run.failed

One or more steps failed.

run.canceled

The run was canceled.

node.completed

A single node finished successfully.

node.failed

A single node failed.

Handler pattern

Always respond 200 OK immediately and process asynchronously. If your handler takes too long, Svix will retry and you may receive duplicate deliveries.

Security

Every webhook is signed with HMAC-SHA256 via Svix. Verify signatures before trusting the payload: