Storyblok · AsyncAPI Specification
Storyblok Webhooks
Version 1
The Storyblok Webhook system delivers real-time event notifications to registered HTTP endpoints when content events occur in a Storyblok space. Events are triggered by actions such as story publication, unpublication, deletion, asset upload, and datasource updates. Webhook payloads are delivered as HTTP POST requests with a JSON body and an optional HMAC-SHA1 signature header for payload integrity verification. Webhooks are configured per space and managed via the Management API or the Storyblok dashboard.
View Spec
View on GitHub
CMSContent DeliveryContent ManagementHeadless CMSImage OptimizationREST APIVisual EditorWebhooksAsyncAPIWebhooksEvents
Channels
/webhook
Receive a Storyblok space event notification
The webhook delivery channel. Storyblok POSTs event payloads to the registered endpoint URL when subscribed actions occur in the space. The endpoint must respond with a 2xx HTTP status code within 120 seconds to be considered a successful delivery. For long-running tasks, respond immediately with 202 Accepted and process asynchronously.
Messages
StoryPublished
Story Published
A story was published in the space.
StoryUnpublished
Story Unpublished
A story was unpublished in the space.
StoryDeleted
Story Deleted
A story was permanently deleted from the space.
StoryMoved
Story Moved
A story was moved to a different folder in the space.
AssetCreated
Asset Created
A new asset was uploaded to the space.
AssetDeleted
Asset Deleted
An asset was deleted from the space.
DatasourceEntriesUpdated
Datasource Entries Updated
Datasource entries were created, updated, or deleted.
Servers
https
customerEndpoint
{webhookUrl}
The customer-defined HTTPS endpoint registered to receive webhook event notifications from Storyblok. The URL is configured when creating a webhook endpoint via the Management API or dashboard.