Skip to content

WebhooksWebhook events and delivery

Webhook events and delivery

A webhook sends an HTTP POST to your server when something happens in Shipmail. Pick the event types you want, and each event arrives as a signed JSON payload.

Last updated

The webhook object

{
  "object": "webhook",
  "id": "whk_abc123",
  "url": "https://example.com/webhooks",
  "events": ["message.received", "message.bounced"],
  "active": true,
  "description": "Production webhook",
  "mailbox_ids": null,
  "domain_ids": null,
  "has_authorization": false,
  "has_standard_webhooks_secret": false,
  "include_reply_text": false,
  "authenticated_senders_only": false,
  "allowed_senders": null,
  "created_at": "2025-01-15T10:00:00.000Z",
  "updated_at": "2025-01-15T10:00:00.000Z"
}

Limits

  • Max 10 webhooks per organization.
  • URLs must use HTTPS.

Use a webhook instead of polling for new mail. If an API key lists new mail at least 1,000 times in a day, Shipmail emails the account owner to suggest one, at most once in 30 days.

Event types

EventDescription
message.receivedSomeone sent an email to one of your mailboxes.
message.sentAn email you sent has left the server.
message.delayedThe receiving server deferred your email. Delivery is retried automatically.
message.deliveredYour email was successfully delivered to the recipient.
message.bouncedYour email could not be delivered. The address may not exist.
message.complainedA recipient marked your email as spam.
mailbox.rule_matchedAn inbox rule with a webhook action matched a new inbound email.
mailbox.export.completedA mailbox export finished and is ready to download.
mailbox.export.failedA mailbox export could not be produced.
reply.overdueA conversation you are waiting on got no reply for 3 days.
conversation.needs_actionThey replied to a conversation you were waiting on, or a follow-up came due.
conversation.reply_target_at_riskA customer is still waiting and a quarter of the reply target remains.
conversation.reply_target_missedA customer is still waiting and the reply target has passed.
calendar.event_startingReminder: a calendar event starts in 15 minutes. For the start itself, use calendar.event_started.
calendar.event_startedA calendar event has started.
calendar.event_endedA calendar event has ended.
calendar.event_createdAn event was added to a calendar.
calendar.event_updatedA calendar event changed: its time, title, place, guests or repeat.
calendar.event_cancelledA calendar event was cancelled or deleted.
calendar.rsvp_updatedA guest accepted, declined or changed a reply.
booking.createdSomeone booked a time through a booking page.
draft.reviewedA person sent or discarded a draft from its review link.
subscriber.addedSomeone joined one of your audiences.
newsletter.sentA newsletter finished sending.
newsletter.recipient.bouncedA newsletter could not be delivered to one of its readers.
newsletter.recipient.complainedA reader marked a newsletter as spam.
newsletter.recipient.unsubscribedA reader unsubscribed through an issue, from its audience or from all your newsletters.
domain.verifiedYour domain's DNS records are correctly configured.
domain.verification_failedOne or more DNS records are missing or incorrect.
domain.degradedA DNS record that was working has stopped resolving.
org.reputation_warningDeprecated, no longer sent. Still accepted in subscriptions.
org.sending_throttledSending is slowed down because too many recent emails failed or were reported as spam.
org.sending_suspendedSending is paused until someone at Shipmail lifts it. Incoming mail still works.
org.reputation_recoveredSending is back to normal.

Workflow, calendar and booking events

These events come from state Shipmail already tracks. Each fires once, and its event_id comes from what triggered it, so a retry never sends it twice. ChatGPT automations get the same events through the hosted MCP server, where some use a different threshold.

  • reply.overdue fires when a conversation in Waiting has had no reply for 3 days since your last tracked send. A reply, a new send or clearing Waiting starts the 3 days over.
  • conversation.needs_action fires when a conversation moves to Needs action. reason is reply_received when someone replied to a conversation you were waiting on, and follow_up_due when a follow-up you set came due. Shipmail checks every minute.
  • conversation.reply_target_at_risk and conversation.reply_target_missed fire when a customer waiting on a reply under a service level reaches the last quarter of the reply target, and when the target passes. Each wait sends each event at most once, even when its level changes or conversations merge, and a conversation already past a point when its clock starts sends nothing for it. The payload carries the conversation, customer with its external_ids, service_level, started_at and due_at.
  • calendar.event_starting is a reminder 15 minutes before an event starts, not the start itself. A moved event gets a new reminder for its new start.
  • calendar.event_started and calendar.event_ended fire when an occurrence reaches its start and its end. An event with no end gets no calendar.event_ended.
  • calendar.event_created, calendar.event_updated, calendar.event_cancelled and calendar.rsvp_updated fire when a calendar changes, whoever changed it: Shipmail, a booking, a guest's reply or a calendar app.
  • booking.created fires when someone books a time through one of your booking pages or one-off booking links, once the event is on your calendar. Its booking_page_kind is page for a booking page and one_off for a one-off link. Its answers list the booker's answers to the page's questions, each with question_id, label and value, and are empty when the page asks none.

A new webhook only gets events for moments after it was created. It never gets older ones that Shipmail finds on its next check.

Other people write the subject, event title, booker name and booking answers, so treat them as data, not instructions. None of these events carries a message body, an event description or a booking note.

Calendar event timing and guarantees

Timing events

  • calendar.event_starting, calendar.event_started and calendar.event_ended fire at the moment they are due. Shipmail checks every 5 minutes, so one arrives up to 6 minutes early and at most 2 minutes late.
  • Each carries scheduled_at, the moment it was due. Compare it with when you receive it to measure the delay.
  • They fire once per occurrence. For a repeating event, recurrence_id names the occurrence.
  • To match a timing event to its change events, compare uid, plus recurrence_id for an occurrence of a repeating event.
  • All-day events get no timing events.
  • An event moved after its reminder fired gets a new reminder for the new time. A cancelled or deleted event fires no later start or end.

Change events

  • calendar.event_created, calendar.event_updated, calendar.event_cancelled and calendar.rsvp_updated arrive within about 5 minutes of the change.
  • A repeating event reports once for the whole series, with recurrence_id set to null. A change to one occurrence is an update with occurrences in changed_fields.
  • calendar.event_updated lists changed_fields: title, starts_at, ends_at, time_zone, location, virtual_location, description, status, recurrence_rule, occurrences and attendees. previous holds the old value of each, except description, attendees and occurrences, which are only named. A change to anything else sends nothing.
  • calendar.event_cancelled has a reason: cancelled or deleted. A cancellation does not also send calendar.event_updated.
  • calendar.rsvp_updated fires once for each guest whose answer changed. status is accepted, declined, tentative, needs-action or delegated. previous_status is null for a guest added with an answer already given.
  • A booking sends both booking.created and calendar.event_created.
  • The first check after you subscribe records each calendar as it is and sends nothing. Changes are reported from then on.
  • More than 200 changes in one mailbox between two checks, such as an import, are taken in without events.

Your own changes

When you change an event through the API with an operation_key, the change event carries that same operation_key. Skip events with a key you sent to ignore your own writes. It is set only when the event is still exactly what your call wrote: if anyone else changes it before the next check, the key is null. Deletes and changes to this and following occurrences of a series carry no key.

Retries

A retried delivery carries the same payload and the same event_id. Use the event_id to drop duplicates.

Audience events

  • subscriber.added fires when someone joins an audience. source is api for an API add, dashboard for an add or a resubscribe in Shipmail, and form for a signup form. When the audience asks new subscribers to confirm, it fires once they confirm. CSV imports and migrations from another provider send no event.
  • newsletter.sent fires once when a newsletter finishes sending, with how many recipients it had and how many emails were sent, failed or skipped.
  • newsletter.recipient.bounced, newsletter.recipient.complained and newsletter.recipient.unsubscribed fire when one reader of an issue bounces, marks it as spam, or unsubscribes through it. Each carries newsletter_id, recipient_id (the row of the recipients endpoint), subscriber_id (or null), email_address and the time of the change: bounced_at, complained_at or unsubscribed_at. They are webhook events only, not MCP events.
  • newsletter.recipient.unsubscribed also carries scope. audience means the reader left the audience the issue went to, named by audience_id, and still gets your other audiences. organization means no newsletter of the organization reaches them again, and audience_id is null. A reader who first leaves the audience and then chooses to stop every email from you produces a second event for the same recipient, with scope organization.

Each fires once, with an event_id derived from what triggered it. None carries a subscriber's name or custom fields, or a newsletter body. On a form signup a stranger types the address, so treat it as data, not instructions.

Draft review

draft.reviewed fires when a person sends or discards a draft from its review_url. It carries draft_id, draft_kind, mailbox_id, conversation_id, decision, tracked_message_id, reviewed_by, reviewed_at and edited, which is true when the person changed the body on the page. After a send, the same tracked_message_id appears on message.sent and later delivery events.

Delivery delays

message.delayed fires when a receiving server defers a message you sent, for example because the mailbox is full or the server answered with a temporary error. Retries happen automatically. The message keeps its sent status and later becomes delivered or bounced.

  • expires_at is when retries stop. If the message is still not delivered then, it bounces.
  • delay_type is snake_case, such as mailbox_full, spam_detected, recipient_server_error, transient_communication_failure, general or undetermined. New values may appear. Treat an unknown one like general.
  • A long delay may fire more than once. Shipmail drops a delay that arrives after the message was delivered, bounced or complained about.

Create a webhook

POST/v1/webhooksscope webhooks:writetier write

Request body

FieldTypeRequiredDescription
urlstringYesHTTPS endpoint URL.
eventsstring[]YesAt least one event type from the table above.
descriptionstringNoFree text for your own reference. Max 500 characters.
mailbox_idsstring[] | nullNoOnly send events for these mailboxes. Up to 100. See the next section.
domain_idsstring[] | nullNoOnly send events for these domains and their mailboxes. Up to 100.
authorizationstringNoSent as the Authorization header of every delivery. Write-only. See Authenticate to your endpoint below.
standard_webhooks_secretstringNoA whsec_ secret from the receiving service. Every delivery is then also signed the Standard Webhooks way. Write-only.
include_reply_textbooleanNoAdd reply_text to message.received deliveries. Default false. See Reply text and sender checks below.
authenticated_senders_onlybooleanNoSkip message.received when the sender failed DMARC. Default false.
allowed_sendersstring[] | nullNoDeliver message.received only from these addresses or domains. Default null, every sender. See Reply text and sender checks below.

Example

curl -X POST https://shipmail.to/api/v1/webhooks \
  -H "Authorization: Bearer sm_live_..." \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com/webhooks", "events": ["message.received"]}'

Returns 201 with the webhook object plus a secret field.

{
  "object": "webhook",
  "id": "whk_abc123",
  "url": "https://example.com/webhooks",
  "events": ["message.received"],
  "active": true,
  "description": null,
  "mailbox_ids": null,
  "domain_ids": null,
  "has_authorization": false,
  "has_standard_webhooks_secret": false,
  "include_reply_text": false,
  "authenticated_senders_only": false,
  "allowed_senders": null,
  "created_at": "2025-01-15T10:00:00.000Z",
  "updated_at": "2025-01-15T10:00:00.000Z",
  "secret": "whsec_..."
}

Limit a webhook to mailboxes or domains

By default a webhook gets its events for every mailbox in the organization. Set mailbox_ids, domain_ids, or both to narrow it. When both are null or empty, nothing is filtered.

  • message.* and mailbox.* events are sent when their mailbox_id is in mailbox_ids, or that mailbox belongs to a domain in domain_ids. A domain also covers mailboxes added later.
  • domain.* events are sent when their domain_id is in domain_ids.
  • org.* events are about the whole organization, so every webhook subscribed to them receives them, filtered or not.

Every ID must belong to your organization. Shipmail rejects unknown IDs with 422 and a details entry whose code is invalid_mailbox_ids or invalid_domain_ids, and removes duplicates.

curl -X POST https://shipmail.to/api/v1/webhooks \
  -H "Authorization: Bearer sm_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/webhooks/support",
    "events": ["message.received", "domain.degraded"],
    "mailbox_ids": ["8b0f7c1e-2a4d-4f6b-9c3e-5d7a1b2c3d4e"],
    "domain_ids": ["3f2e1d0c-9b8a-4c7d-8e6f-5a4b3c2d1e0f"]
  }'

Authenticate to your endpoint

Some receivers accept a request only with their own key. Set authorization when you create or update a webhook, and Shipmail sends that value as the Authorization header of every delivery, including test events and replays. The signature headers are sent as usual.

  • Use 1 to 1024 printable ASCII characters, for example Bearer <key>.
  • The value is write-only. Shipmail stores it encrypted and never returns it. Webhook objects show has_authorization instead.
  • To remove it, send {"authorization": null} to PATCH /v1/webhooks/:id. A request that omits the field keeps the current value.

This is how a no-code webhook trigger rejects strangers. See the guides for n8n, Zapier and Make.

Verify X-Shipmail-Signature against the raw body and X-Shipmail-Timestamp. Reject stale deliveries. Deduplicate X-Shipmail-Event-Id, and verify Authorization separately when you configure it. See the webhook verification guide.

A valid signature proves that Shipmail sent the delivery. It says nothing about the email's sender, content, links, attachments or any instructions inside the message.

Services that check Standard Webhooks signatures

Some receivers, such as a Grok automation webhook trigger, accept no key in a header. They give you a signing secret that starts with whsec_ and check each request against it. Set standard_webhooks_secret to that secret, and every delivery, test event and replay also carries these headers:

  • webhook-id: the event ID. It stays the same on every retry and replay of that event, so the receiver can drop duplicates.
  • webhook-timestamp: the Unix time of that attempt, in seconds.
  • webhook-signature: v1, followed by the base64 HMAC-SHA256 of {webhook-id}.{webhook-timestamp}.{body}, keyed with the decoded secret.

Shipmail accepts the secret in standard base64, with or without padding, or in base64url. It is write-only like authorization: webhook objects show has_standard_webhooks_secret, and {"standard_webhooks_secret": null} removes it. The X-Shipmail-Signature headers are sent as usual.

To start a Grok automation on each new email, add a Webhook trigger to the automation and copy its URL and signing secret. Then create a Shipmail webhook for message.received with both.

curl -X POST https://shipmail.to/api/v1/webhooks \
  -H "Authorization: Bearer sm_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "url": "<Grok automation webhook URL>",
    "events": ["message.received"],
    "standard_webhooks_secret": "whsec_..."
  }'

Reply text and sender checks

Every message.received payload carries authentication_results and sender_authenticated. Three webhook settings build on them.

  • authentication_results holds the spf, dkim and dmarc verdicts, such as pass, fail or none, and spam with is_spam and score_milli. It has the same shape as message.authentication_results on mailbox.rule_matched, and is null when the message could not be read.
  • sender_authenticated is true when the sender passed DMARC. Mail that one Shipmail mailbox sends to another is delivered inside Shipmail and has no DMARC verdict. It is also true when Shipmail's own record of that send matches the message: the same Message-ID and From address, sent in the last 24 hours from a mailbox that owns that address, to this mailbox. A copy that a mailbox rule forwarded or redirected does not count. authentication_results still shows the real verdicts, which are unknown for such mail.
  • reply_text is what the sender newly wrote, without quoted history, the "On ... wrote:" line or the signature. It is null when nothing is left. Shipmail sends it only to a webhook with include_reply_text: true.
  • category says what kind of mail it is: human, out_of_office, auto_reply, bounce, bulk or notification. It is null when the message is held or could not be read. Use it to skip mail no person wrote. It comes from headers the sender controls, so never use it as a security decision. With include_reply_text: true, out_of_office_until gives the day the sender says they are back, as YYYY-MM-DD, read from replies in English, French, German and Spanish, and mentioned_contacts lists up to 5 addresses an out-of-office or automatic reply names, each { email, name }, without the sender, the mailbox and your own domains. It is null for other categories.
  • security carries the original deterministic scan verdict, risk codes, scanner name, exact content hash, and a null review. When API-agent security hold is enabled, flagged and unscannable deliveries omit reply text. A replay keeps the verdict stored with the original delivery. Fetch the message to see its current review.

Deliveries stored before these fields existed do not have them, so treat them as optional.

Who can turn on reply text

reply_text carries the content of the email, so turning on include_reply_text needs permission to read that mail. In the dashboard, you need access to the mailboxes the webhook covers. An API key must also grant messages:read, or the request fails with 403. The same check applies when you change the URL, events, mailboxes or domains of a webhook that includes reply text. A key without messages:read sees stored deliveries without reply_text.

Only authenticated senders

Anyone can put any address in the From line. With authenticated_senders_only: true, Shipmail does not deliver message.received to that webhook when sender_authenticated is false. Other events are unaffected. Turn it on for an agent that acts on mail, for example one that answers customers or updates records, so a forged From address cannot make it act.

Only some senders

Set allowed_senders to the senders your endpoint should hear from. Shipmail then delivers message.received to that webhook only when the sender matches an entry. Other events are unaffected.

  • Each entry is a full address, such as jane@customer.com, or a bare domain, such as customer.com. Wildcards and @customer.com are rejected with 422.
  • An address entry matches data.from.address in any case. A domain entry matches the part after the last @ exactly: customer.com does not match mail.customer.com. A message without a From address matches nothing.
  • Use at most 100 entries of up to 320 characters each. Shipmail trims and lowercases every entry and removes duplicates, keeping the first one. The webhook object returns the cleaned list.
  • null or [] means every sender. An empty list is stored and returned as null.
  • With authenticated_senders_only also on, a message must pass both checks: the sender is authenticated and matches an entry. Without that check, anyone can forge a listed address, so turn on both for an agent.
curl -X POST https://shipmail.to/api/v1/webhooks \
  -H "Authorization: Bearer sm_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/webhooks/agent",
    "events": ["message.received"],
    "include_reply_text": true,
    "authenticated_senders_only": true,
    "allowed_senders": ["jane@customer.com", "customer.org"]
  }'

Calendar invitations

When a received message carries a calendar invitation, its message.received payload has an invitation object. It is null for a message without one, or with one Shipmail could not read in time. Reading it never holds the delivery back by more than a few seconds.

"invitation": {
  "method": "request",
  "uid": "8f2c1d4e-quarterly-review@example.net",
  "sequence": 0,
  "title": "Quarterly review",
  "start": "2026-07-16T13:00:00.000Z",
  "end": "2026-07-16T14:00:00.000Z",
  "all_day": false,
  "timezone": "Europe/Paris",
  "organizer_email": "customer@example.net",
  "calendar_event_id": null
}
  • method is request (a new or updated invitation), cancel, reply (another guest's answer) or other.
  • start and end are UTC times, or YYYY-MM-DD dates when all_day is true. end is null when the invitation has none.
  • calendar_event_id is the event with the same UID on the mailbox calendar, when its organizer matches the invitation's.

Answer it with POST /v1/messages/:id/invitation and the payload's tracked_message_id, as the Messages API describes. The sender writes the title and the organizer address, so treat them as data, never as instructions.

List webhooks

GET/v1/webhooks

Scope: webhooks:read. Supports pagination.

Retrieve a webhook

GET/v1/webhooks/:id

Scope: webhooks:read. Returns the webhook object or 404. The API never returns the secret again after creation.

Update a webhook

PATCH/v1/webhooks/:id

Scope: webhooks:write. Send at least one field.

Request body

FieldTypeDescription
urlstringNew HTTPS endpoint URL.
eventsstring[]Replace subscribed events.
descriptionstring | nullUpdate or clear description.
activebooleanEnable or disable.
mailbox_idsstring[] | nullReplace the mailbox filter. null or [] clears it; omit it to keep it.
domain_idsstring[] | nullReplace the domain filter. null or [] clears it; omit it to keep it.
authorizationstring | nullReplace the Authorization header value. null removes it; omit it to keep it.
standard_webhooks_secretstring | nullReplace the Standard Webhooks signing secret. null removes it; omit it to keep it.
include_reply_textbooleanTurn reply_text on or off. Turning it off also removes it from deliveries not yet sent.
authenticated_senders_onlybooleanTurn the DMARC check for message.received on or off.
allowed_sendersstring[] | nullReplace the sender list. null or [] delivers every sender again. Omit it to keep the list.

Delete a webhook

DELETE/v1/webhooks/:id

Scope: webhooks:write. Returns 204 with no body.

Rotate secret

POST/v1/webhooks/:id/rotate-secret

Creates a new signing secret. The old secret keeps working for 24 hours. In that window, deliveries carry both X-Shipmail-Signature (new secret) and X-Shipmail-Signature-Previous (old secret).

{
  "secret": "whsec_...",
  "previous_secret_expires_at": "2025-01-16T10:00:00.000Z"
}

Send test event

POST/v1/webhooks/:id/test

Queues a webhook.test event and returns 202 with the event ID. Shipmail signs and retries the test like a real event.

{
  "event_id": "evt_abc123"
}

List deliveries

GET/v1/webhooks/:id/deliveries

Scope: webhooks:read. Supports pagination and optional status (pending, delivered, failed) and event_type query filters.

The delivery object

{
  "object": "webhook_delivery",
  "id": "dlv_abc123",
  "event_id": "evt_abc123",
  "event_type": "message.received",
  "mode": "live",
  "status": "delivered",
  "attempts": 1,
  "last_status_code": 200,
  "last_error": null,
  "created_at": "2025-01-15T10:00:00.000Z",
  "delivered_at": "2025-01-15T10:00:01.000Z"
}

Retrieve and replay a delivery

GET/v1/webhooks/:id/deliveries/:delivery_id

Returns the delivery object plus the exact payload, next_attempt_at, and replayed_from_delivery_id.

POST/v1/webhooks/:id/deliveries/:delivery_id/replay

Scope: webhooks:write. Replays only a failed delivery that uses the current webhook contract. The replay gets a new delivery ID and keeps the original event ID, event type and payload. Send an Idempotency-Key header if you retry this API request. A pending or delivered source, an inactive webhook or a legacy payload returns 409.

Retry schedule

Shipmail saves each delivery before it queues it for background processing. Two rules apply.

  • Per-event retries. Shipmail tries each delivery up to 5 times, waiting 1 minute, 5 minutes, 30 minutes, then 4 hours between attempts.
  • Endpoint auto-disable. When a webhook's 5 most recent deliveries have all failed, Shipmail disables it and emails its owners. Turn it back on with Enable in the webhook's menu in the dashboard, or by updating the webhook with active: true. Fix the endpoint first: until a delivery succeeds, another failed delivery can disable it again. Shipmail does not send events from the time the webhook was disabled.

Endpoint auto-disable

When a webhook's 5 most recent deliveries have all failed, the endpoint is disabled and its owners are emailed. Re-enable it from the webhook's menu in the dashboard, or by updating the webhook with active set to true.

Verifying signatures

Shipmail signs every webhook delivery. Check the signature on your endpoint to confirm the request came from Shipmail and nobody changed it on the way. See the webhook verification guide for the signature scheme and code examples in TypeScript and Python.

Event payloads

Each delivery holds an event object with the structure below. The data field depends on the event type. The current contract version is 2026-09-10. The test field is true only for synthetic sandbox or webhook-test traffic. This version was a hard cutover, and Shipmail's runtime contract rejects unknown envelope and event-data fields.

Message events distinguish tracked_message_id (the Shipmail database resource), email_id (the provider/JMAP email ID), and rfc_message_id (the RFC header value). Use message.received when an agent needs every inbound event. When the email replies to one of your transactional sends, message.received carries in_reply_to_tracked_message_id, the tracked_message_id of that send. For any other email, or when its headers name more than one of your transactional sends, the field is absent.

message.received also carries in_reply_to and references: every Message-ID in the email's own In-Reply-To and References headers, in header order, formatted like rfc_message_id (<id@host>). Use them to match a reply to an email your app sent with its own Message-ID. The sender writes these headers, so treat them as a hint, never as proof. Deliveries stored before they existed omit them.

Events that name a conversation carry both conversation_id and thread_id. Store conversation_id: it is Shipmail's own identifier and it survives thread merges and mail-server re-threading. thread_id is deprecated. It keeps working and its value is unchanged.

message.received

Someone sent an email to one of your mailboxes.

{
  "version": "2026-09-10",
  "event_id": "evt_received",
  "event_type": "message.received",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "tracked_message_id": "msg_example",
    "mailbox_id": "mbx_example",
    "client_reference": "crm-123",
    "rfc_message_id": "<crm-123@example.com>",
    "email_id": "eml_example",
    "from": {
      "address": "customer@example.net",
      "name": "Customer"
    },
    "to": [
      {
        "address": "hello@example.com",
        "name": "Example Team"
      }
    ],
    "cc": [],
    "bcc": [],
    "subject": "Hello",
    "thread_id": "thr_provider_example",
    "conversation_id": "thd_example",
    "received_at": "2026-07-12T12:00:00.000Z",
    "in_reply_to_tracked_message_id": "msg_transactional_example",
    "in_reply_to": [
      "<order-1042-2@notify.example.com>"
    ],
    "references": [
      "<order-1042-1@notify.example.com>",
      "<order-1042-2@notify.example.com>"
    ],
    "reply_text": "Thursday at 2pm works for us. I'll send the signed order form before then.",
    "category": "human",
    "out_of_office_until": null,
    "mentioned_contacts": null,
    "authentication_results": {
      "spf": "pass",
      "dkim": "pass",
      "dmarc": "pass",
      "spam": {
        "is_spam": false,
        "score_milli": -1200
      }
    },
    "sender_authenticated": true,
    "invitation": {
      "method": "request",
      "uid": "8f2c1d4e-quarterly-review@example.net",
      "sequence": 0,
      "title": "Quarterly review",
      "start": "2026-07-16T13:00:00.000Z",
      "end": "2026-07-16T14:00:00.000Z",
      "all_day": false,
      "timezone": "Europe/Paris",
      "organizer_email": "customer@example.net",
      "calendar_event_id": null
    }
  }
}

message.sent

An email you sent has left the server.

{
  "version": "2026-09-10",
  "event_id": "evt_sent",
  "event_type": "message.sent",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "tracked_message_id": "msg_example",
    "mailbox_id": "mbx_example",
    "client_reference": "crm-123",
    "rfc_message_id": "<crm-123@example.com>",
    "email_id": "010201-example",
    "from": {
      "address": "hello@example.com",
      "name": "Example Team"
    },
    "to": [
      {
        "address": "customer@example.net",
        "name": "Customer"
      }
    ],
    "cc": [],
    "bcc": [],
    "subject": "Hello",
    "sent_at": "2026-07-12T12:00:00.000Z"
  }
}

message.delayed

The receiving server deferred your email. Delivery is retried automatically.

{
  "version": "2026-09-10",
  "event_id": "evt_delayed",
  "event_type": "message.delayed",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "tracked_message_id": "msg_example",
    "mailbox_id": "mbx_example",
    "client_reference": "crm-123",
    "rfc_message_id": "<crm-123@example.com>",
    "email_id": "010201-example",
    "from": {
      "address": "hello@example.com",
      "name": "Example Team"
    },
    "to": [
      {
        "address": "customer@example.net",
        "name": "Customer"
      }
    ],
    "cc": [],
    "bcc": [],
    "subject": "Hello",
    "delayed_at": "2026-07-12T12:00:00.000Z",
    "delay_type": "mailbox_full",
    "expires_at": "2026-07-13T12:00:00.000Z",
    "recipients": [
      {
        "email_address": "customer@example.net",
        "status": "delayed",
        "diagnostic_code": "smtp; 452 4.2.2 mailbox full"
      }
    ]
  }
}

message.delivered

Your email was successfully delivered to the recipient.

{
  "version": "2026-09-10",
  "event_id": "evt_delivered",
  "event_type": "message.delivered",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "tracked_message_id": "msg_example",
    "mailbox_id": "mbx_example",
    "client_reference": "crm-123",
    "rfc_message_id": "<crm-123@example.com>",
    "email_id": "010201-example",
    "from": {
      "address": "hello@example.com",
      "name": "Example Team"
    },
    "to": [
      {
        "address": "customer@example.net",
        "name": "Customer"
      }
    ],
    "cc": [],
    "bcc": [],
    "subject": "Hello",
    "delivered_at": "2026-07-12T12:00:00.000Z",
    "recipients": [
      {
        "email_address": "customer@example.net",
        "status": "delivered",
        "smtp_response": "250 2.0.0 OK",
        "remote_mta_ip": "203.0.113.10",
        "processing_time_ms": 842
      }
    ]
  }
}

message.bounced

Your email could not be delivered. The address may not exist.

{
  "version": "2026-09-10",
  "event_id": "evt_bounced",
  "event_type": "message.bounced",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "tracked_message_id": "msg_example",
    "mailbox_id": "mbx_example",
    "client_reference": "crm-123",
    "rfc_message_id": "<crm-123@example.com>",
    "email_id": "010201-example",
    "from": {
      "address": "hello@example.com",
      "name": "Example Team"
    },
    "to": [
      {
        "address": "customer@example.net",
        "name": "Customer"
      }
    ],
    "cc": [],
    "bcc": [],
    "subject": "Hello",
    "bounce_type": "permanent",
    "bounce_subtype": "General",
    "bounced_at": "2026-07-12T12:00:00.000Z",
    "recipients": [
      {
        "email_address": "customer@example.net",
        "action": "failed",
        "status": "5.1.1",
        "diagnostic_code": "smtp; 550 5.1.1 mailbox does not exist",
        "suppressed": true
      }
    ]
  }
}

message.complained

A recipient marked your email as spam.

{
  "version": "2026-09-10",
  "event_id": "evt_complained",
  "event_type": "message.complained",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "tracked_message_id": "msg_example",
    "mailbox_id": "mbx_example",
    "client_reference": "crm-123",
    "rfc_message_id": "<crm-123@example.com>",
    "email_id": "010201-example",
    "from": {
      "address": "hello@example.com",
      "name": "Example Team"
    },
    "to": [
      {
        "address": "customer@example.net",
        "name": "Customer"
      }
    ],
    "cc": [],
    "bcc": [],
    "subject": "Hello",
    "complaint_feedback_type": "abuse",
    "complained_at": "2026-07-12T12:00:00.000Z",
    "recipients": [
      {
        "email_address": "customer@example.net",
        "suppressed": true
      }
    ]
  }
}

mailbox.rule_matched

An inbox rule with a webhook action matched a new inbound email.

{
  "version": "2026-09-10",
  "event_id": "evt_rule_matched",
  "event_type": "mailbox.rule_matched",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "mailbox_id": "mbx_example",
    "mailbox_address": "hello@example.com",
    "rule_id": "4f5a9d74-b0f1-49a7-bbfb-1f2af841f5b2",
    "rule_name": "Important invoices",
    "action_index": 1,
    "matched_at": "2026-07-12T12:00:00.000Z",
    "message": {
      "id": "eml_example",
      "thread_id": "thr_provider_example",
      "conversation_id": "thd_example",
      "subject": "Invoice ready",
      "from": [
        {
          "name": "Vendor",
          "email": "billing@example.net"
        }
      ],
      "to": [
        {
          "name": null,
          "email": "hello@example.com"
        }
      ],
      "received_at": "2026-07-12T12:00:00.000Z",
      "has_attachment": true,
      "size": 4096,
      "authentication_results": {
        "spf": "pass",
        "dkim": "pass",
        "dmarc": "pass",
        "spam": {
          "is_spam": false,
          "score_milli": 100
        }
      }
    }
  }
}

mailbox.export.completed

A mailbox export finished and is ready to download.

{
  "version": "2026-09-10",
  "event_id": "evt_export_completed",
  "event_type": "mailbox.export.completed",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "object": "mailbox_export",
    "id": "mbexp_example",
    "mailbox_id": "mbx_example",
    "status": "completed",
    "format": "zip",
    "format_version": 1,
    "file_size": 4194304,
    "message_count": 1284,
    "folder_count": 9,
    "error_code": null,
    "download_url": "https://exports.shipmail.to/mbexp_example.zip?signature=example",
    "download_url_expires_at": "2026-07-12T18:00:00.000Z",
    "expires_at": "2026-07-19T12:00:00.000Z",
    "created_at": "2026-07-12T12:00:00.000Z",
    "started_at": "2026-07-12T12:00:00.000Z",
    "completed_at": "2026-07-12T12:00:00.000Z"
  }
}

mailbox.export.failed

A mailbox export could not be produced.

{
  "version": "2026-09-10",
  "event_id": "evt_export_failed",
  "event_type": "mailbox.export.failed",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "object": "mailbox_export",
    "id": "mbexp_example",
    "mailbox_id": "mbx_example",
    "status": "failed",
    "format": "zip",
    "format_version": 1,
    "file_size": null,
    "message_count": null,
    "folder_count": null,
    "error_code": "source_unavailable",
    "download_url": null,
    "download_url_expires_at": null,
    "expires_at": null,
    "created_at": "2026-07-12T12:00:00.000Z",
    "started_at": "2026-07-12T12:00:00.000Z",
    "completed_at": "2026-07-12T12:00:00.000Z"
  }
}

reply.overdue

A conversation you are waiting on got no reply for 3 days.

{
  "version": "2026-09-10",
  "event_id": "evt_reply_overdue",
  "event_type": "reply.overdue",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "mailbox_id": "mbx_example",
    "mailbox_address": "hello@example.com",
    "conversation_id": "thd_example",
    "thread_id": "T1a2b3c",
    "subject": "Proposal",
    "tracked_message_id": "msg_example",
    "waiting_on": [
      {
        "address": "customer@example.net",
        "name": "Customer"
      }
    ],
    "waiting_since": "2026-07-09T12:00:00.000Z",
    "overdue_at": "2026-07-12T12:00:00.000Z",
    "after_days": 3
  }
}

conversation.needs_action

They replied to a conversation you were waiting on, or a follow-up came due.

{
  "version": "2026-09-10",
  "event_id": "evt_needs_action",
  "event_type": "conversation.needs_action",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "mailbox_id": "mbx_example",
    "mailbox_address": "hello@example.com",
    "conversation_id": "thd_example",
    "thread_id": "T1a2b3c",
    "subject": "Re: Proposal",
    "reason": "reply_received",
    "email_id": "Mb1c2d3",
    "latest_from": "customer@example.net",
    "entered_at": "2026-07-12T12:00:00.000Z"
  }
}

conversation.reply_target_at_risk

A customer is still waiting and a quarter of the reply target remains.

{
  "version": "2026-09-10",
  "event_id": "evt_reply_target_at_risk",
  "event_type": "conversation.reply_target_at_risk",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "mailbox_id": "mbx_example",
    "mailbox_address": "hello@example.com",
    "conversation_id": "thd_example",
    "thread_id": "T1a2b3c",
    "subject": "Invoice question",
    "customer": {
      "id": "cust_example",
      "name": "Acme",
      "external_ids": [
        {
          "source": "hubspot",
          "external_id": "1234",
          "url": "https://app.hubspot.com/contacts/1/company/1234"
        }
      ]
    },
    "service_level": {
      "id": "svl_example",
      "name": "Premium",
      "reply_target_minutes": 240
    },
    "started_at": "2026-07-12T08:00:00.000Z",
    "due_at": "2026-07-12T12:00:00.000Z"
  }
}

conversation.reply_target_missed

A customer is still waiting and the reply target has passed.

{
  "version": "2026-09-10",
  "event_id": "evt_reply_target_missed",
  "event_type": "conversation.reply_target_missed",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "mailbox_id": "mbx_example",
    "mailbox_address": "hello@example.com",
    "conversation_id": "thd_example",
    "thread_id": "T1a2b3c",
    "subject": "Invoice question",
    "customer": {
      "id": "cust_example",
      "name": "Acme",
      "external_ids": [
        {
          "source": "hubspot",
          "external_id": "1234",
          "url": "https://app.hubspot.com/contacts/1/company/1234"
        }
      ]
    },
    "service_level": {
      "id": "svl_example",
      "name": "Premium",
      "reply_target_minutes": 240
    },
    "started_at": "2026-07-12T08:00:00.000Z",
    "due_at": "2026-07-12T12:00:00.000Z"
  }
}

calendar.event_starting

Reminder: a calendar event starts in 15 minutes. For the start itself, use calendar.event_started.

{
  "version": "2026-09-10",
  "event_id": "evt_event_starting",
  "event_type": "calendar.event_starting",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "mailbox_id": "mbx_example",
    "mailbox_address": "hello@example.com",
    "calendar_id": "b",
    "event_id": "e1",
    "uid": "3b8e0c27-weekly-review@example.com",
    "recurrence_id": null,
    "title": "Weekly review",
    "starts_at": "2026-07-12T12:15:00.000Z",
    "ends_at": "2026-07-12T12:45:00.000Z",
    "time_zone": "Europe/Lisbon",
    "minutes_before": 15,
    "scheduled_at": "2026-07-12T12:00:00.000Z"
  }
}

calendar.event_started

A calendar event has started.

{
  "version": "2026-09-10",
  "event_id": "evt_event_started",
  "event_type": "calendar.event_started",
  "created_at": "2026-07-12T12:15:00.000Z",
  "test": false,
  "data": {
    "mailbox_id": "mbx_example",
    "mailbox_address": "hello@example.com",
    "calendar_id": "b",
    "event_id": "e1",
    "uid": "3b8e0c27-weekly-review@example.com",
    "recurrence_id": null,
    "title": "Weekly review",
    "starts_at": "2026-07-12T12:15:00.000Z",
    "ends_at": "2026-07-12T12:45:00.000Z",
    "time_zone": "Europe/Lisbon",
    "scheduled_at": "2026-07-12T12:15:00.000Z"
  }
}

calendar.event_ended

A calendar event has ended.

{
  "version": "2026-09-10",
  "event_id": "evt_event_ended",
  "event_type": "calendar.event_ended",
  "created_at": "2026-07-12T12:45:00.000Z",
  "test": false,
  "data": {
    "mailbox_id": "mbx_example",
    "mailbox_address": "hello@example.com",
    "calendar_id": "b",
    "event_id": "e1",
    "uid": "3b8e0c27-weekly-review@example.com",
    "recurrence_id": null,
    "title": "Weekly review",
    "starts_at": "2026-07-12T12:15:00.000Z",
    "ends_at": "2026-07-12T12:45:00.000Z",
    "time_zone": "Europe/Lisbon",
    "scheduled_at": "2026-07-12T12:45:00.000Z"
  }
}

calendar.event_created

An event was added to a calendar.

{
  "version": "2026-09-10",
  "event_id": "evt_event_created",
  "event_type": "calendar.event_created",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "mailbox_id": "mbx_example",
    "mailbox_address": "hello@example.com",
    "calendar_id": "b",
    "event_id": "e3",
    "uid": "7f9c1a52-3d4e-4b8a-9c11-2f6d0e5b8a71",
    "recurrence_id": null,
    "title": "Project kickoff",
    "starts_at": "2026-07-15T10:00:00.000Z",
    "ends_at": "2026-07-15T10:30:00.000Z",
    "time_zone": "Europe/Lisbon",
    "is_recurring": false,
    "detected_at": "2026-07-12T12:00:00.000Z",
    "operation_key": null
  }
}

calendar.event_updated

A calendar event changed: its time, title, place, guests or repeat.

{
  "version": "2026-09-10",
  "event_id": "evt_event_updated",
  "event_type": "calendar.event_updated",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "mailbox_id": "mbx_example",
    "mailbox_address": "hello@example.com",
    "calendar_id": "b",
    "event_id": "e3",
    "uid": "7f9c1a52-3d4e-4b8a-9c11-2f6d0e5b8a71",
    "recurrence_id": null,
    "title": "Project kickoff",
    "starts_at": "2026-07-15T10:00:00.000Z",
    "ends_at": "2026-07-15T10:30:00.000Z",
    "time_zone": "Europe/Lisbon",
    "is_recurring": false,
    "detected_at": "2026-07-12T12:00:00.000Z",
    "operation_key": null,
    "changed_fields": [
      "starts_at",
      "ends_at",
      "attendees"
    ],
    "previous": {
      "starts_at": "2026-07-14T09:00:00.000Z",
      "ends_at": "2026-07-14T09:30:00.000Z"
    }
  }
}

calendar.event_cancelled

A calendar event was cancelled or deleted.

{
  "version": "2026-09-10",
  "event_id": "evt_event_cancelled",
  "event_type": "calendar.event_cancelled",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "mailbox_id": "mbx_example",
    "mailbox_address": "hello@example.com",
    "calendar_id": "b",
    "event_id": "e3",
    "uid": "7f9c1a52-3d4e-4b8a-9c11-2f6d0e5b8a71",
    "recurrence_id": null,
    "title": "Project kickoff",
    "starts_at": "2026-07-15T10:00:00.000Z",
    "ends_at": "2026-07-15T10:30:00.000Z",
    "time_zone": "Europe/Lisbon",
    "is_recurring": false,
    "detected_at": "2026-07-12T12:00:00.000Z",
    "operation_key": null,
    "reason": "cancelled"
  }
}

calendar.rsvp_updated

A guest accepted, declined or changed a reply.

{
  "version": "2026-09-10",
  "event_id": "evt_rsvp_updated",
  "event_type": "calendar.rsvp_updated",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "mailbox_id": "mbx_example",
    "mailbox_address": "hello@example.com",
    "calendar_id": "b",
    "event_id": "e3",
    "uid": "7f9c1a52-3d4e-4b8a-9c11-2f6d0e5b8a71",
    "recurrence_id": null,
    "title": "Project kickoff",
    "starts_at": "2026-07-15T10:00:00.000Z",
    "ends_at": "2026-07-15T10:30:00.000Z",
    "time_zone": "Europe/Lisbon",
    "is_recurring": false,
    "detected_at": "2026-07-12T12:00:00.000Z",
    "operation_key": null,
    "attendee_email": "guest@example.net",
    "attendee_name": "Guest",
    "status": "accepted",
    "previous_status": "needs-action"
  }
}

booking.created

Someone booked a time through a booking page.

{
  "version": "2026-09-10",
  "event_id": "evt_booking_created",
  "event_type": "booking.created",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "mailbox_id": "mbx_example",
    "mailbox_address": "hello@example.com",
    "booking_page_id": "bkp_example",
    "booking_page_name": "Intro call",
    "booking_page_kind": "page",
    "event_id": "e2",
    "starts_at": "2026-07-14T09:00:00.000Z",
    "ends_at": "2026-07-14T09:30:00.000Z",
    "duration_minutes": 30,
    "time_zone": "Europe/Lisbon",
    "booker": {
      "address": "customer@example.net",
      "name": "Customer"
    },
    "answers": [
      {
        "question_id": "q_phone",
        "label": "Phone number",
        "value": "+351 912 345 678"
      }
    ],
    "created_at": "2026-07-12T12:00:00.000Z"
  }
}

draft.reviewed

A person sent or discarded a draft from its review link.

{
  "version": "2026-09-10",
  "event_id": "evt_draft_reviewed",
  "event_type": "draft.reviewed",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "draft_id": "drf_example",
    "draft_kind": "reply",
    "mailbox_id": "mbx_example",
    "conversation_id": "thd_example",
    "decision": "sent",
    "tracked_message_id": "msg_example",
    "reviewed_by": "approver@example.com",
    "reviewed_at": "2026-07-12T12:00:00.000Z",
    "edited": false
  }
}

subscriber.added

Someone joined one of your audiences.

{
  "version": "2026-09-10",
  "event_id": "evt_subscriber_added",
  "event_type": "subscriber.added",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "audience_id": "aud_example",
    "audience_name": "Product updates",
    "subscriber_id": "audmem_example",
    "email_address": "reader@example.net",
    "source": "form",
    "created_at": "2026-07-12T12:00:00.000Z"
  }
}

newsletter.sent

A newsletter finished sending.

{
  "version": "2026-09-10",
  "event_id": "evt_newsletter_sent",
  "event_type": "newsletter.sent",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "newsletter_id": "nws_example",
    "subject": "July update",
    "audience_id": "aud_example",
    "recipient_count": 1200,
    "sent_count": 1195,
    "failed_count": 2,
    "skipped_count": 3,
    "sent_at": "2026-07-12T12:00:00.000Z"
  }
}

newsletter.recipient.bounced

A newsletter could not be delivered to one of its readers.

{
  "version": "2026-09-10",
  "event_id": "evt_newsletter_recipient_bounced",
  "event_type": "newsletter.recipient.bounced",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "newsletter_id": "nws_example",
    "recipient_id": "nwsrcp_example",
    "subscriber_id": "audmem_example",
    "email_address": "reader@example.net",
    "bounced_at": "2026-07-12T12:05:00.000Z"
  }
}

newsletter.recipient.complained

A reader marked a newsletter as spam.

{
  "version": "2026-09-10",
  "event_id": "evt_newsletter_recipient_complained",
  "event_type": "newsletter.recipient.complained",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "newsletter_id": "nws_example",
    "recipient_id": "nwsrcp_example",
    "subscriber_id": "audmem_example",
    "email_address": "reader@example.net",
    "complained_at": "2026-07-12T12:05:00.000Z"
  }
}

newsletter.recipient.unsubscribed

A reader unsubscribed through an issue, from its audience or from all your newsletters.

{
  "version": "2026-09-10",
  "event_id": "evt_newsletter_recipient_unsubscribed",
  "event_type": "newsletter.recipient.unsubscribed",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "newsletter_id": "nws_example",
    "recipient_id": "nwsrcp_example",
    "subscriber_id": "audmem_example",
    "email_address": "reader@example.net",
    "scope": "audience",
    "audience_id": "aud_example",
    "unsubscribed_at": "2026-07-12T12:05:00.000Z"
  }
}

domain.verified

Your domain's DNS records are correctly configured.

{
  "version": "2026-09-10",
  "event_id": "evt_domain_verified",
  "event_type": "domain.verified",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "domain_id": "dom_example",
    "domain_name": "example.com",
    "verified_at": "2026-07-12T12:00:00.000Z"
  }
}

domain.verification_failed

One or more DNS records are missing or incorrect.

{
  "version": "2026-09-10",
  "event_id": "evt_domain_failed",
  "event_type": "domain.verification_failed",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "domain_id": "dom_example",
    "domain_name": "example.com",
    "records": {
      "mx": true,
      "spf": false,
      "dkim": true,
      "dmarc": true
    },
    "checked_at": "2026-07-12T12:00:00.000Z"
  }
}

domain.degraded

A DNS record that was working has stopped resolving.

{
  "version": "2026-09-10",
  "event_id": "evt_domain_degraded",
  "event_type": "domain.degraded",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "domain_id": "dom_example",
    "domain_name": "example.com",
    "failed_records": [
      "spf"
    ],
    "degraded_at": "2026-07-12T12:00:00.000Z"
  }
}

org.reputation_warning

Deprecated, no longer sent. Still accepted in subscriptions.

{
  "version": "2026-09-10",
  "event_id": "evt_reputation_warning",
  "event_type": "org.reputation_warning",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "previous_status": "healthy",
    "new_status": "warning",
    "statistics": {
      "window_days": 7,
      "total_sent": 1000,
      "hard_bounces": 35,
      "complaints": 1,
      "bounce_rate": 0.035,
      "complaint_rate": 0.001
    }
  }
}

org.sending_throttled

Sending is slowed down because too many recent emails failed or were reported as spam.

{
  "version": "2026-09-10",
  "event_id": "evt_reputation_throttled",
  "event_type": "org.sending_throttled",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "previous_status": "warning",
    "new_status": "throttled",
    "statistics": {
      "window_days": 7,
      "total_sent": 1000,
      "hard_bounces": 35,
      "complaints": 1,
      "bounce_rate": 0.035,
      "complaint_rate": 0.001
    }
  }
}

org.sending_suspended

Sending is paused until someone at Shipmail lifts it. Incoming mail still works.

{
  "version": "2026-09-10",
  "event_id": "evt_reputation_suspended",
  "event_type": "org.sending_suspended",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "previous_status": "throttled",
    "new_status": "suspended",
    "statistics": {
      "window_days": 7,
      "total_sent": 1000,
      "hard_bounces": 35,
      "complaints": 1,
      "bounce_rate": 0.035,
      "complaint_rate": 0.001
    }
  }
}

org.reputation_recovered

Sending is back to normal.

{
  "version": "2026-09-10",
  "event_id": "evt_reputation_recovered",
  "event_type": "org.reputation_recovered",
  "created_at": "2026-07-12T12:00:00.000Z",
  "test": false,
  "data": {
    "previous_status": "warning",
    "new_status": "healthy",
    "statistics": {
      "window_days": 7,
      "total_sent": 1000,
      "hard_bounces": 35,
      "complaints": 1,
      "bounce_rate": 0.035,
      "complaint_rate": 0.001
    }
  }
}