Command
nylas deliverability send-events message
Show every recipient's send timeline for one message.
Written by Qasim Muhammad Staff SRE
What does nylas deliverability send-events message do?
The nylas deliverability send-events message command shows every recipient's send timeline for one message, with each recipient's current status (delivered, bounced, complaint) and the events that led there. It covers only messages sent from an Agent Account or through Transactional send; messages from connected grants such as Google or Microsoft accounts are not included. It answers whether a given message reached each recipient.
Usage
nylas deliverability send-events message <message-id> [--json]Flags
| Flag | Description |
|---|---|
| --json | Output as JSON |
| --no-color | Disable color output |
| --verbose(-v) | Enable verbose output |
| --config | Custom config file path |
| --help(-h) | Show help for the command |
| --limit | Limit results (most list commands) |
| --yes(-y) | Skip confirmations |
Examples
The nylas deliverability send-events message command shows every recipient's send timeline for one message, with each recipient's current status (delivered, bounced, complaint) and the events that led there.
Timeline for a Transactional send (Message-ID header)
nylas deliverability send-events message "<abc@mail.example.com>"Timeline as JSON
nylas deliverability send-events message "<abc@mail.example.com>" --jsonExample output
Message ID: <abc@mail.example.com>
From: agent@mail.example.com
Sent: 2026-10-29 16:13:54 UTC
Last event: 2026-10-29 16:13:55 UTC
alice@example.org [delivered]
2026-10-29 16:13:54 UTC accepted
2026-10-29 16:13:55 UTC delivered 250 2.0.0 OKTroubleshooting
Message ID with angle brackets fails or matches nothing
For a Transactional send the message ID is the Message-ID header, angle brackets included. Quote it in the shell, for example "<abc@mail.example.com>". The CLI percent-encodes it for the API.
403 api.forbidden: this endpoint requires an application API key
These commands are application-level. Configure an API key with nylas auth config or NYLAS_API_KEY; a grant access token is rejected.
no send activity found in the last 90 days
The message was sent more than 90 days ago, was sent from a connected grant rather than an Agent Account or Transactional send, or the ID is wrong.
Recommended guides
Track Email Opens, Clicks, and Replies
Send tracked email and receive open, click, and reply events over webhooks from the terminal. Verify the signatures, and learn why email open rates overcount.
SMTP Reply Codes Explained
Decode SMTP reply codes: 2xx success, 4xx transient retry, 5xx permanent. Read bounce DSN enhanced codes and debug delivery from the terminal.
Email Bounce Codes Reference (DSN)
Decode bounce DSNs: RFC 3463 enhanced status codes (5.1.1, 5.2.2, 4.x.x), hard vs soft bounces, and finding them with nylas email search from:mailer-daemon.
Validate Email Addresses from the CLI
Validate email addresses from the terminal with an RFC 5322 syntax check and a dig MX lookup, then gate nylas email send to cut hard bounces.
AI Agent Email Bounce Detection and Retry
Deterministic bounce rules for AI agents: classify soft vs hard from DSN codes, retry 4.x.x with backoff, suppress 5.x.x, and escalate edge cases to humans.
Soft Bounce vs Hard Bounce Explained
Soft bounces (4xx) are transient and retried for up to 5 days; hard bounces (5xx) are permanent. Code ranges, suppression rules, and terminal detection with the CLI.
Run nylas deliverability send-events message --help for full help output.