Webhooks
Webhooks
Webhooks tell your systems what happens in Mestra as it happens. When a run finishes, or a reviewer approves, Mestra sends a small message to a web address you choose. Your system can then fetch the details with the API.
Each message is an event. It says what happened and where to look. It doesn’t carry your artwork, comment text, names or file names.
The events for screens that run Mestra Player are listed with the Mestra Player webhooks.
How it works
- An owner adds an endpoint: an
httpsaddress, and the events it wants. - Mestra sends each matching event to it as a
POST, signed with the endpoint’s secret. - Your system checks the signature, answers with a
2xxstatus, and does its work. - If it doesn’t answer
2xx, Mestra tries again.
An event looks like this:
{ "id": "evt_…", "object": "event", "type": "run.completed", "created": "2026-10-22T03:14:15Z", "data": { "object": { "id": "…", "type": "run", "url": "https://app.withmestra.com/api/v1/runs/…" } }}The event object page describes every field, and event types lists them all.
What you can see
Owners see two tabs under Webhooks in Mestra:
- Endpoints: each endpoint with its log of deliveries, a Resend button and Send test event.
- Events: every event from the last 30 days, with where it was delivered.
A key can also read the same events from the API. See Test and resend.
Where to start
Only owners can add endpoints.