Twilio Segment · AsyncAPI Specification
Segment Webhook Events
Version 1.0.0
Segment Webhooks submit real-time user data to HTTP endpoints as POST requests. When configured as a destination, Segment forwards identify, track, page, screen, group, and alias events to up to five webhook URLs. Each event is delivered as a JSON payload via HTTP POST with a configurable shared secret for authentication. The receiving service must respond within 5 seconds. If no response is received, Segment logs a timeout error and retries the event.
View Spec
View on GitHub
CompanyCustomer Data PlatformCDPIdentity ResolutionEvent StreamingReverse ETLData PipelineCustomer DataAnalyticsAcquiredAsyncAPIEventsWebhooks
Channels
/webhook
Receive Segment event
The webhook endpoint that receives Segment events. Segment sends each event as an HTTP POST request with a JSON body.
Messages
IdentifyEvent
Identify Event
An identify event that associates a user with their traits.
TrackEvent
Track Event
A track event that records an action performed by a user.
PageEvent
Page Event
A page event that records a page view on a website.
ScreenEvent
Screen Event
A screen event that records a screen view in a mobile app.
GroupEvent
Group Event
A group event that associates a user with a group or account.
AliasEvent
Alias Event
An alias event that merges two user identities.
Servers
https
webhookEndpoint
{webhookUrl}
Your webhook endpoint URL configured in the Segment Webhooks destination settings. Up to five webhook URLs can be configured.
AsyncAPI Specification
Work with this as data
Every AsyncAPI spec here is available over the APIs.io API and to AI agents over MCP.