Webhook events

Every webhook event AI Inbx sends: one page per event with its payload schema, the signature headers, the answer that settles it, and an example body.

What an endpoint receives: one request per event, each signed, in the envelope every event shares.

Events

Event	Fires when
`email.received`	Inbound mail arrived and was matched onto a thread, once per received message.
`email.sent`	A message was handed to the mail provider: acceptance, not delivery.
`email.delivered`	The receiving server accepted the message, reported per recipient.
`email.bounced`	Delivery to one or more recipients failed; a hard bounce writes a suppression.
`email.complained`	A recipient marked the message as spam, which weighs on sending reputation.
`email.failed`	The mail provider refused the message before any delivery attempt.
`email.unsubscribed`	A recipient opted out by link, one-click header, or reply.
`email.opened`	A tracked open was recorded, with bot and privacy-proxy hits flagged.
`email.clicked`	A tracked link was clicked, with bot and scanner hits flagged.
`thread.created`	A new conversation started: an inbound message, a send, or a forward.
`domain.verified`	A domain’s DKIM identity was verified, and the domain can send.
`domain.lost`	A verified domain’s DKIM record stopped resolving.
`mailbox.connected`	A customer finished authorizing a Gmail or Outlook mailbox.
`mailbox.needs_reauth`	A mailbox’s stored authorization stopped working.
`mailbox.disconnected`	A mailbox was removed, by you or by the customer revoking access.

Check each delivery’s signature before trusting it: see Verifying.