AsyncAPI channel · Storyblok · Storyblok Webhooks

`/webhook`

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.

Open source AsyncAPI → All Storyblok channels Storyblok provider profile

Provider: Storyblok AsyncAPI: v2.6.0 Spec: Storyblok Webhooks Operations: 1 Messages: 7

Channel address

/webhook

Operations

publish

receiveStoryblokEvent

Receive a Storyblok space event notification

Messages

StoryPublished

A story was published in the space.

Content-Type: application/json

StoryUnpublished

A story was unpublished in the space.

Content-Type: application/json

StoryDeleted

A story was permanently deleted from the space.

Content-Type: application/json

StoryMoved

A story was moved to a different folder in the space.

Content-Type: application/json

AssetCreated

A new asset was uploaded to the space.

Content-Type: application/json

AssetDeleted

An asset was deleted from the space.

Content-Type: application/json

DatasourceEntriesUpdated

Datasource entries were created, updated, or deleted.

Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.