Email activity
Email Activity is the operational view for messages sent through Lettermint. Use it to search recent messages, inspect delivery events, view message content, and understand delivery issues.

Search and filter
Use the message list to find messages by sender, recipient, subject, status, project, route, tag, or date range. This is the fastest way to answer "what happened to this email?"
Message details
Open a message to review:
- Current status
- Sender and recipients
- Project, route, and tag
- Delivery event timeline
- Webhook-related events
- Bounce, complaint, suppression, and failure metadata
- Available source, HTML, and plain-text content

Status for messages with multiple recipients
A message has one status, even when it has several recipients in to, cc or bcc. Each recipient result can raise that status, and the highest-ranked result wins:
| Rank | Status |
|---|---|
| 1 (highest) | spam_complaint |
| 2 | hard_bounced |
| 3 | failed |
| 4 | clicked |
| 5 | opened |
| 6 | delivered |
| 7 (lowest) | soft_bounced |
For example, if one recipient's mail is delivered and another hard bounces, the message status is hard_bounced. If one recipient opens the email and another only receives it, the status is opened.
- Recipients that don't have a result yet don't pull the status down.
- The order in which results arrive doesn't matter.
- The status can change later, but only upwards in the ranking. A
soft_bouncedmessage becomesdeliveredonce a retry succeeds, and anopenedmessage never goes back todelivered. - Opens and clicks from security scanners and other bots don't change the status.
- An unsubscribe is recorded as an
unsubscribedevent, but doesn't change the message status.
The message status alone can't tell you how each recipient did. For per-recipient results, use GET /v1/messages/{messageId}/events: each delivery event has the recipient in metadata.recipient. You can also listen for webhook events, which include a recipient field.
Deliverability insights
When available for your plan and message, Lettermint surfaces delivery and spam insights. Use these to spot missing plaintext, large bodies, suspicious links, missing unsubscribe handling, or sender/domain issues.
The spam score is the combined weight of the rules matched during the message scan. Lower scores indicate a cleaner message:
| Spam score | Interpretation |
|---|---|
| Below 5 | Clean |
| 5 through 10 | Potential spam markers |
| Above 10 and below 15 | Likely spam |
| 15 or higher | Definite spam |
A null score means that no spam assessment is available for the message. Spam scores and detailed symbols are available on plans with Spam Insights.

Team API access
The Team API exposes read-only message endpoints for automation:
GET /v1/messagesGET /v1/messages/{messageId}GET /v1/messages/{messageId}/eventsGET /v1/messages/{messageId}/sourceGET /v1/messages/{messageId}/htmlGET /v1/messages/{messageId}/text
These endpoints require read:messages.
For plans with Spam Insights, message list items and message details include spam_score. Individual message details also include spam_symbols, which describe the rules contributing to the score. These fields work the same way for sent and received messages.
Next steps
- Webhook events - Match dashboard events to webhook payloads
- Suppressions - Understand blocked recipients
- Data retention - Understand how long message data is available