Command
nylas deliverability send-events timeseries
Show send counts and rates per day, week, or month.
Written by Qasim Muhammad Staff SRE
What does nylas deliverability send-events timeseries do?
The nylas deliverability send-events timeseries command shows send counts and bounce and complaint rates per day, week, or month across a window of up to 365 days. 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. Use --granularity auto to pick day, week, or month from the window length.
Usage
nylas deliverability send-events timeseries [--granularity auto|day|week|month] [--start YYYY-MM-DD] [--end YYYY-MM-DD] [--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 |
| --end | Last UTC day, YYYY-MM-DD, inclusive (default: today) |
| --granularity | Bucket size: auto, day, week, month (default auto: day ≤21 days, week ≤92, else month) |
| --sending-domain | Only this sending domain |
| --start | First UTC day, YYYY-MM-DD (default: 6 days before --end) |
Examples
The nylas deliverability send-events timeseries command shows send counts and bounce and complaint rates per day, week, or month across a window of up to 365 days.
Weekly buckets since August
nylas deliverability send-events timeseries --granularity week --start 2026-08-01Daily buckets as JSON
nylas deliverability send-events timeseries --granularity day --jsonTroubleshooting
invalid --start value on a metrics command
Metrics windows take UTC dates in YYYY-MM-DD form, both days included, and can span at most 365 days. Unix timestamps and look-backs are for the activity list commands only.
A rate shows a dash instead of 0%
A dash means the rate has no denominator in the window (for example no sends), so there is no data. It is not a 0% rate.
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 timeseries --help for full help output.