The customer-configured callback endpoint. MailerLite invokes it with HTTP
POST and a JSON body. The shape of the body depends on the event `type` /
`event` field, and on whether the webhook was registered with
`batchable: true` (in which case events are wrapped in a `BatchedEnvelope`).
A subscriber's custom fields were updated or subscription was confirmed.
Content-Type: application/json
subscriber.unsubscribed
A subscriber unsubscribed from the account.
Content-Type: application/json
subscriber.bounced
A subscriber's email address bounced.
Content-Type: application/json
subscriber.spam_reported
A subscriber marked a campaign as spam. This is the closest documented
equivalent to a "complaint" event in the MailerLite webhook catalog.
Content-Type: application/json
subscriber.added_to_group
A subscriber was added to a group.
Content-Type: application/json
subscriber.removed_from_group
A subscriber was removed from a group.
Content-Type: application/json
subscriber.automation_triggered
A subscriber entered an automation workflow.
Content-Type: application/json
subscriber.automation_completed
A subscriber completed an automation workflow.
Content-Type: application/json
campaign.sent
A campaign finished sending to all recipients.
Content-Type: application/json
batched.events
When a webhook is registered with `batchable: true`, MailerLite may
deliver multiple events in a single HTTP POST wrapped in a batched
envelope. Each element of the `events` array retains its standard
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.