AsyncAPI channel · FullStory · FullStory Webhook Events

/webhook

Channel for all FullStory webhook event deliveries. Events are sent as HTTP POST requests to the configured endpoint URL with a JSON payload containing the event name, version, and event-specific data.

Open source AsyncAPI → All FullStory channels FullStory provider profile
Provider: FullStory AsyncAPI: v2.6.0 Spec: FullStory Webhook Events Operations: 1 Messages: 4

Channel address

/webhook

Operations

publish
receiveWebhookEvent
Receive webhook event notifications from FullStory

Messages

segment.created
Sent when a FullStory user creates a new segment in the platform
Content-Type: application/json
segment.trend.alert
Sent when a segment-based alert triggers because the active users in a saved segment cross a configured threshold
Content-Type: application/json
recording.event.custom
Sent when a custom event has been processed. Custom events are created during recording via the FS.event Browser API function.
Content-Type: application/json
note.created
Sent when a note is created in FullStory on a session recording
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.