AsyncAPI channel · Mixpanel · Mixpanel Webhooks

/mixpanel/cohort-sync

Subscriber endpoint that receives Mixpanel Cohort Sync membership change notifications. Mixpanel POSTs one JSON payload per page of a sync run. The payload's `action` field identifies whether the call is a full membership load (`members`), an incremental add (`add_members`), or an incremental removal (`remove_members`).

Open source AsyncAPI → All Mixpanel channels Mixpanel provider profile
Provider: Mixpanel AsyncAPI: v2.6.0 Spec: Mixpanel Webhooks Operations: 1 Messages: 3

Channel address

/mixpanel/cohort-sync

Operations

publish
receiveMixpanelCohortSync
Receive a Mixpanel Cohort Sync webhook

Messages

CohortMembers
Full membership snapshot of a cohort, sent on first sync and on refresh.
Content-Type: application/json
CohortAddMembers
Incremental add of cohort members since the previous sync.
Content-Type: application/json
CohortRemoveMembers
Incremental removal of cohort members since the previous sync.
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.