AsyncAPI 2.6 description of MailerLite's outbound webhook surface. MailerLite delivers event notifications by issuing HTTP POST requests with a JSON body to a callback URL the customer registers through the Webhooks API (`POST /api/webhooks`). Each delivery carries a `Signature` header whose value is the HMAC-SHA256 of the raw JSON payload, computed with the webhook's secret. Source documentation: - Webhooks overview: https://developers.mailerlite.com/docs/webhooks.html Delivery and retry behavior (per the official docs): - Endpoint must respond with a 2XX status within 3 seconds. - On non-2XX (or timeout) responses, MailerLite retries the same delivery up to three additional times at 10, 100, and 1000-second intervals. Event-type coverage: Only the event types explicitly listed in the official MailerLite webhooks documentation are modelled here. The originally requested events `subscriber.complained` and `subscriber.added_through_webform` are NOT published by MailerLite and have been omitted to avoid fabrication. The closest documented equivalent to "complained" is `subscriber.spam_reported`, which is included.
View SpecView on GitHubEmail MarketingAutomationNewslettersSubscribersAsyncAPIWebhooksEvents
Channels
/
publishreceiveMailerLiteEvent
Receive a MailerLite webhook event
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`).
Messages
✉
SubscriberCreated
Subscriber created
A new subscriber was added to the account.
✉
SubscriberUpdated
Subscriber updated
A subscriber's custom fields were updated or subscription was confirmed.
✉
SubscriberUnsubscribed
Subscriber unsubscribed
A subscriber unsubscribed from the account.
✉
SubscriberBounced
Subscriber bounced
A subscriber's email address bounced.
✉
SubscriberSpamReported
Subscriber reported spam
A subscriber marked a campaign as spam. This is the closest documented equivalent to a "complaint" event in the MailerLite webhook catalog.
✉
SubscriberAddedToGroup
Subscriber added to group
A subscriber was added to a group.
✉
SubscriberRemovedFromGroup
Subscriber removed from group
A subscriber was removed from a group.
✉
SubscriberAutomationTriggered
Subscriber automation triggered
A subscriber entered an automation workflow.
✉
SubscriberAutomationCompleted
Subscriber automation completed
A subscriber completed an automation workflow.
✉
CampaignSent
Campaign sent
A campaign finished sending to all recipients.
✉
BatchedEvents
Batched events envelope
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 per-event structure.
Servers
https
customer-endpoint{webhookUrl}
The subscriber-supplied HTTPS endpoint registered with MailerLite via `POST /api/webhooks` (field `url`). MailerLite POSTs each event payload to this URL.