Single delivery channel. Klaviyo POSTs a `WebhookDelivery` envelope to
the subscriber URL for every subscribed topic. The envelope's `data[]`
array contains one entry per event, each carrying its `topic` string.
Profile manually unsuppressed for email marketing.
Content-Type: application/json
UpdatedEmailPreferences
Profile updated their email preferences.
Content-Type: application/json
SentSms
SMS was sent to the recipient.
Content-Type: application/json
ReceivedSms
Inbound SMS received from a profile.
Content-Type: application/json
ClickedSms
Recipient clicked a link within an SMS.
Content-Type: application/json
FailedToDeliverSms
SMS could not be delivered.
Content-Type: application/json
SubscribedToSmsMarketing
Profile granted SMS marketing consent.
Content-Type: application/json
UnsubscribedFromSmsMarketing
Profile revoked SMS marketing consent.
Content-Type: application/json
ReceivedPush
Recipient received a push notification.
Content-Type: application/json
BouncedPush
Push notification sent but not delivered.
Content-Type: application/json
OpenedPush
Recipient tapped on a push notification.
Content-Type: application/json
ReadyToReview
Product is ready for the customer to review.
Content-Type: application/json
SubmittedRating
Customer submitted a product rating.
Content-Type: application/json
SubmittedReview
Customer submitted a product review.
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.