Mixpanel Webhooks
Version 1.0.0
AsyncAPI 2.6 description of Mixpanel's outbound webhook surfaces. Mixpanel delivers two distinct, documented webhook event streams to customer-hosted HTTPS endpoints: 1. Alert Webhooks (Custom Alerts) - Mixpanel POSTs a JSON payload to a configured Notification Webhook URL whenever a Custom Alert on a report fires. Alerts are configured per project under Project Settings > Integrations > Notification Webhook, and individual alerts route to one of the configured webhooks in addition to (or instead of) email and Slack channels. 2. Cohort Sync Custom Webhooks - Mixpanel POSTs JSON membership change payloads to a configured webhook URL whenever a Cohort Sync runs. Each sync produces one of three actions ("members" for the initial or refresh load, "add_members" for incremental adds, "remove_members" for incremental removes). Syncs run on a 30-minute cadence and large cohorts are paginated across multiple POSTs sharing a `mixpanel_session_id`. Mixpanel retries 5xx and 429 responses up to five times over 60 seconds with exponential backoff; 4xx responses (400, 401, 403, 404) pause the sync until manual intervention. Add and remove operations are batched at 1000 members per call. Source documentation: - Alerts overview (notification channels and webhook setup): https://docs.mixpanel.com/docs/features/alerts - Cohort Sync overview: https://docs.mixpanel.com/docs/cohort-sync/overview - Cohort Sync Custom Webhooks: https://docs.mixpanel.com/docs/cohort-sync/webhooks Out of scope - not modelled here: - Data Pipelines (S3, GCS, Azure Blob, BigQuery, Databricks, Redshift Spectrum, Snowflake) deliver data as files into object storage or as rows into a warehouse on an hourly or daily batch cadence. They do not push to subscriber webhooks and therefore are not an AsyncAPI surface. - Native Cohort Sync integrations (Braze, Iterable, Marketo, Facebook Ads, Google Ads, OneSignal, Segment, mParticle, etc.) call each partner's own API rather than a customer-controlled webhook URL. Only the Custom Webhook destination is modelled here. - The `Send Live API` referenced in the request prompt is not present in the public developer documentation surveyed (developer.mixpanel.com llms.txt index and docs.mixpanel.com data-pipelines section) and has therefore been omitted to avoid fabrication.
Channels
Messages
Servers
{webhookUrl}