PlatformGovern
Your systems know the moment something happens
Register a URL and choose the events: Muvia POSTs them, signed. Every attempt lands in a delivery log you can read.
https://hooks.example.com/muvia
Delivery log
- sources.sync_failedDelivered10:14
- sources.sync_recoveredDelivered10:31
- post_processing.flow_run_failedGiven up11:02
Illustrative example
Events you can verify, deliveries you can follow
Signed events
Each POST carries an HMAC-SHA256 signature that includes the timestamp: the receiver checks where it came from and can discard a replayed message.
Delivery log
For each delivery: status, attempts, the response outcome and the payload sent. The log can be filtered and exported to xlsx.
Retries
If the receiver does not answer with a 2xx, Muvia retries with growing waits, up to six attempts. An endpoint that keeps failing is switched off.
Checked destinations
Muvia refuses URLs that are not https or that lead to internal addresses, and checks again on every attempt.
From first endpoint to verification
- 01
Register the endpoint
A name, an https URL and the events to subscribe to. The signing secret is shown once.
- 02
Verify the signature
The receiver recomputes the HMAC-SHA256 with the secret and compares it with the X-Muvia-Signature header.
- 03
Follow the deliveries
The log shows what was sent and how it was answered; you can pause, resume or rotate the secret.
In detail
- Events
- The same as the app's notifications, for example a source copy that failed or recovered, or a flow run that failed.
- Security
- Security notifications about individual accounts are never sent to a webhook.
- Headers
- X-Muvia-Event, X-Muvia-Event-Id, X-Muvia-Delivery-Id and X-Muvia-Signature.
- Expected answer
- A 2xx within 10 seconds.
- Payload
- No recipients, usernames or email addresses.
- Secret
- Shown once; when you rotate it, the old one stops working at once.
Frequently asked questions
In rare cases, yes: a webhook is a notice, not a ledger. If you cannot miss anything, reconcile your data with the read-only API.
It can happen: delivery is at least once. The event id stays the same across every attempt, so the receiver can recognise a duplicate.
Muvia retries with growing waits, then gives the delivery up. After five given-up deliveries in a row the endpoint is switched off; you switch it back on from the panel.
Bring us a question you can't answer today.
We start from a real question your business has and walk the path from source to dashboard with your systems, not a demo dataset.