Skip to main content

Event Types

Email Events​

EventDescription
email.sentEmail was successfully delivered to the SMTP server
email.failedEmail delivery failed after all retries
email.unsubscribedRecipient unsubscribed via a one-click link
email.complainedRecipient filed a spam complaint
email.inboundAn inbound email was received (see Inbound Email)

Web Form Message Events​

EventDescription
message.receivedA web form submission passed scanning (see Web Form Messages)
message.spamA web form submission was quarantined or rejected by scanning
message.repliedAn operator replied to a web form message
message.reply_receivedThe sender answered a web form thread by email

Campaign Events​

EventDescription
campaign.startedA campaign began sending
campaign.completedA campaign finished sending all messages

Payload Shapes​

email.sent​

Fired when an email is successfully delivered to the SMTP server:

{
  "event": "email.sent",
  "email_id": "550e8400-e29b-41d4-a716-446655440000",
  "timestamp": "2026-01-01T00:00:01Z"
}

email.failed​

Fired when delivery fails after all retries:

{
  "event": "email.failed",
  "email_id": "550e8400-e29b-41d4-a716-446655440000",
  "timestamp": "2026-01-01T00:00:01Z"
}

email.unsubscribed​

Fired when a recipient opts out via a one-click unsubscribe link:

{
  "event": "email.unsubscribed",
  "email_uuid": "550e8400-e29b-41d4-a716-446655440000",
  "email": "recipient@example.com",
  "list_id": 7,
  "timestamp": "2026-01-01T00:00:01Z"
}

list_id is omitted when the unsubscribe is not scoped to a specific subscriber list.

email.complained​

Fired when a spam complaint is recorded (e.g. via the bounce webhook):

{
  "event": "email.complained",
  "email_uuid": "550e8400-e29b-41d4-a716-446655440000",
  "email": "recipient@example.com",
  "timestamp": "2026-01-01T00:00:01Z"
}

campaign.started​

Fired when a campaign begins sending:

{
  "event": "campaign.started",
  "campaign_id": 42,
  "name": "Spring Newsletter",
  "timestamp": "2026-01-01T00:00:01Z"
}

campaign.completed​

Fired when a campaign finishes sending all of its messages:

{
  "event": "campaign.completed",
  "campaign_id": 42,
  "name": "Spring Newsletter",
  "timestamp": "2026-01-01T00:00:01Z"
}

Inbound Email​

The email.inbound event fires when Posta receives an incoming message on a verified domain. Its payload is richer than the outbound events:

{
  "event": "email.inbound",
  "timestamp": "2026-01-01T00:00:01Z",
  "inbound_id": "7d3f9a12-...",
  "from": "sender@example.com",
  "to": ["inbox@yourdomain.com"],
  "subject": "Hello",
  "text_body": "Plain text body",
  "html_body": "<p>HTML body</p>",
  "headers": { "Reply-To": "sender@example.com" },
  "attachments": [
    {
      "filename": "report.pdf",
      "content_type": "application/pdf",
      "size": 12345,
      "url": "https://..."
    }
  ],
  "size": 14200,
  "message_id": "<unique@mail.example.com>",
  "source": "smtp",
  "received_at": "2026-01-01T00:00:00Z"
}

For configuring inbound routing and managing received messages, see the Inbound Email section in the sidebar.

Web Form Messages​

message.received and message.spam share one payload. It carries the full submission plus the scan verdict, so a downstream system can apply its own policy without calling back:

{
  "event": "message.received",
  "timestamp": "2026-01-01T00:00:01Z",
  "message_id": "b0b1c2d3-...",
  "form_id": "3f9a7d12-...",
  "form_name": "Contact form",
  "sender_email": "ada@example.com",
  "sender_name": "Ada Lovelace",
  "sender_phone": "+1 555 010 9999",
  "subject": "Question about pricing",
  "body": "How does per-seat billing work?",
  "fields": [
    { "key": "name", "value": "Ada Lovelace" },
    { "key": "email", "value": "ada@example.com" },
    { "key": "phone", "value": "+1 555 010 9999" },
    { "key": "message", "value": "How does per-seat billing work?" }
  ],
  "status": "received",
  "spam_score": 0,
  "scan_reasons": [],
  "client_ip": "203.0.113.7",
  "received_at": "2026-01-01T00:00:00Z"
}

sender_phone is present only when the form submitted one. status is received or flagged for message.received, and quarantined for message.spam. Submissions scored past the reject threshold are stored for audit but never dispatched.

message.replied and message.reply_received​

Both carry one thread reply. kind is operator for message.replied and inbound for message.reply_received:

{
  "event": "message.reply_received",
  "timestamp": "2026-01-02T09:00:01Z",
  "message_id": "b0b1c2d3-...",
  "reply_id": "7c1e9a40-...",
  "form_id": "3f9a7d12-...",
  "form_name": "Contact form",
  "kind": "inbound",
  "from": "ada@example.com",
  "to": "msg+k3j2...@reply.example.com",
  "subject": "Re: Question about pricing",
  "text_body": "Thanks, that answers it.",
  "sender_mismatch": false,
  "created_at": "2026-01-02T09:00:00Z"
}

message_id is the thread's original submission. An operator reply also carries email_id, the outbound email whose delivery status is in the email log. sender_mismatch is true when an emailed answer came from an address other than the original submitter.

For configuring forms and replying to submissions, see the Forms & Messages section in the sidebar.