AsyncAPI channel · Amplitude · Amplitude Webhooks and Cohort Sync

/webhooks/streaming

The Webhooks Streaming destination. Amplitude POSTs one JSON payload per HTTP request to the configured webhook URL. The destination can be configured to forward event payloads, user payloads, or both; subscribers receive one of two message shapes, discriminated by the presence of `event_type` (event payload) vs. absence of `event_type` with a user identity present (user payload). Payloads may als

Open source AsyncAPI → All Amplitude channels Amplitude provider profile
Provider: Amplitude AsyncAPI: v2.6.0 Spec: Amplitude Webhooks and Cohort Sync Operations: 1 Messages: 2

Channel address

/webhooks/streaming

Operations

publish
receiveAmplitudeWebhook
Receive an Amplitude Webhooks Streaming payload.

Messages

WebhookEvent
Default Amplitude event payload forwarded by the Webhooks Streaming destination.
Content-Type: application/json
WebhookUser
Default Amplitude user payload forwarded by the Webhooks Streaming destination.
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.