Storage Webhooks
Storage webhooks
When storage items are created, updated, or deleted, the API can send webhook notifications to endpoints you configure via the Monolith webhooks API. Use this to keep external systems in sync with storage changes (e.g. audit logs, asset management).
Event type
Storage webhooks use the event type storage. When creating or updating a webhook, include "storage" in the events array to receive storage-related payloads.
When webhooks are sent
create
A new storage item is created (POST /storage).
update
A storage item is updated (PATCH /storage/:uuid or assign-to-case).
delete
A storage item is deleted (DELETE /storage/:uuid).
Payload shape
Each webhook request is an HTTP POST to your configured URL with a JSON body like:
action
string
One of: create, update, delete.
type
string
Event resource type; always "storage" for storage webhooks.
timestamp
string
ISO 8601 time when the event occurred.
webhook_timestamp
string
ISO 8601 time when the webhook was sent.
webhook_uuid
string
UUID of the webhook configuration that triggered this delivery.
data
object
The storage item (same shape as in list/get).
updated_from
object
(Update only.) Previous values for fields that changed; may be partial.
Example: create
Example: update (with updated_from)
Example: delete
Headers and signature
Monolith-Event — The event type (e.g.
storage).Monolith-signature — HMAC signature of the raw JSON body using your webhook secret, so you can verify the request came from Monolith. Verify this before trusting the payload.
Webhook subscription, URL, and secret are configured through the Monolith webhooks API (create/update webhook with events: ["storage"]).
Last updated