AsyncAPI channel · Mailchimp
· Mailchimp Marketing Webhooks
/
The single callback path the consumer registered with Mailchimp. All six event types are delivered to this same URL; subscribers discriminate on the `type` form field.
Channel address
/
Operations
publish
receiveAudienceWebhookEvent
Receive Mailchimp audience webhook events.
Messages
subscribe
A new subscriber was added to a list.
Content-Type:
application/x-www-form-urlencodedunsubscribe
A list member unsubscribed or was removed.
Content-Type:
application/x-www-form-urlencodedprofile
A subscriber's profile was updated.
Content-Type:
application/x-www-form-urlencodedcleaned
A subscriber's email address was cleaned from the list.
Content-Type:
application/x-www-form-urlencodedupemail
A subscriber's email address was changed.
Content-Type:
application/x-www-form-urlencodedcampaign
A campaign was sent or cancelled.
Content-Type:
application/x-www-form-urlencodedAbout 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 Agent Skill and MCP server surfaces of the same providers.