Send events to your own systems as they happen.
Send SAMRISK events to your other tools.
£10 a month on its own, or included in Business
Building created, task completed, audit completed, visitor signed in, incident reported. Choose which of the 98 events each webhook receives.
Each request carries an X-Webhook-Signature header: an HMAC-SHA256 of the body, made with your webhook's secret. Check it to know the request came from SAMRISK.
Deliveries go out from a queue checked every 30 seconds, with a 10-second timeout. Each attempt is logged with its status code, response and time taken. There are no automatic retries.
Real screens
How webhooks looks in SAMRISK, on the example estate.
The example estate; records are illustrative.
Feeds it
It feeds
Compute an HMAC-SHA256 of the raw request body with your webhook's secret and compare the hex result with the X-Webhook-Signature header.
JSON with event, data, timestamp and company_id. The data holds the record's id, its table, the operation and a few key fields.
The delivery fails, it is logged with its response, and the webhook's failure count goes up. There are no retries, so that event is not sent again. The count resets on the next successful delivery.
No. You can point a webhook at any HTTPS address that accepts a POST, including a Zapier catch hook.
Not yet. A public API is coming. For now, use webhooks to send events to other systems, and export buildings, tasks, audits, documents, incidents, items, visitors and material call-offs to CSV or XLSX.