Source: https://cli.nylas.com/docs/commands/deliverability-send-events-list # nylas deliverability send-events list List send events (newest first). Written by [Qasim Muhammad](https://cli.nylas.com/authors/qasim-muhammad) Staff SRE Published November 3, 2026 Updated November 3, 2026 ## What does nylas deliverability send-events list do? The nylas deliverability send-events list command shows send activity, newest first: accepted, delivered, bounced, complaint, and rejected events with the recipient and the SMTP or bounce reason. 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. Filter by event type, recipient, recipient domain, sending domain, or message, and page with --page-token. ## Usage ```bash nylas deliverability send-events list [--event-type TYPE]... [--recipient-domain DOMAIN] [--start TIME] [--end TIME] [--page-token TOKEN] [--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(-n) | Maximum number of items to show | | --yes(-y) | Skip confirmations | | --bounce-class | Bounce class: hard, soft, or undetermined | | --end | Window end, inclusive, within the last 90 days; a date means the end of that UTC day (same formats; default: now) | | --event-type | Event type, repeatable: accepted, delivered, bounced, complaint, rejected | | --from | From address | | --grant-id | Only events for this grant (agent account) | | --message-id | Message ID | | --order | Sort order: desc (newest first, default) or asc | | --page-token | Page token for pagination | | --recipient | Recipient address | | --recipient-domain | Recipient domain | | --sending-domain | Sending domain | | --start | Window start: Unix seconds, YYYY-MM-DD, "YYYY-MM-DD HH:MM[:SS]" or YYYY-MM-DDTHH:MM[:SS] (UTC), RFC3339, or look-back like 24h/7d (default: UTC midnight 6 days before --end, or before today) | | --thread-id | Thread ID | ## Examples The nylas deliverability send-events list command shows send activity, newest first: accepted, delivered, bounced, complaint, and rejected events with the recipient and the SMTP or bounce reason. ### Hard bounces in the last 24 hours ```bash nylas deliverability send-events list --event-type bounced --bounce-class hard --start 24h ``` ### Bounces and complaints for one recipient domain ```bash nylas deliverability send-events list --recipient-domain gmail.com --event-type bounced --event-type complaint ``` ### Every event for one message as JSON ```bash nylas deliverability send-events list --message-id "" --json ``` ## Example output ```text TIME EVENT RECIPIENT FROM REASON EVENT ID 2026-10-29 16:13:55 UTC delivered alice@example.org agent@mail.example.com 250 2.0.0 OK 0d7b9a8cd937c8e0b1cd511b31b0fc516fee3864f5d6890ad8a655d4d6f30c23 2026-10-29 16:13:20 UTC bounced (hard) bob@example.net agent@mail.example.com General (5.1.1) c4e6a8b0d2f41638507a9cbe1d3f5a7c9e0b2d4f6a8c1e3b5d7f9a0c2e4b6d8f Next page token: eyJ0IjoiMjAyNi0xMC0yOVQxNjoxMzoyMFoifQ ``` ## Troubleshooting ### 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. ### invalid --start value Use Unix seconds, YYYY-MM-DD (a whole UTC day), YYYY-MM-DD HH:MM[:SS] or YYYY-MM-DDTHH:MM[:SS] in UTC, RFC3339, or a look-back such as 24h or 7d. Words such as today or 9am are not accepted because they change between runs. ### page_token is not valid for this request A page token only works with the exact same filters, --start and --end. After a look-back such as --start 7d, use the Next page line the CLI prints, which repeats the resolved times as Unix seconds. ### --end is more than 90 days ago Activity is kept for 90 days. Use a more recent --end; for older trends, use the summary, timeseries, or breakdown metrics commands instead. ## Related commands [nylas deliverability send-alerts createCreate a send alert rule.](https://cli.nylas.com/docs/commands/deliverability-send-alerts-create) [nylas deliverability send-alerts deleteDelete a send alert rule.](https://cli.nylas.com/docs/commands/deliverability-send-alerts-delete) [nylas deliverability send-alerts listList send alert rules.](https://cli.nylas.com/docs/commands/deliverability-send-alerts-list) [nylas deliverability send-alerts showShow a send alert rule.](https://cli.nylas.com/docs/commands/deliverability-send-alerts-show) [nylas deliverability send-alerts updateChange a send alert rule; flags you leave out keep their value.](https://cli.nylas.com/docs/commands/deliverability-send-alerts-update) [nylas deliverability send-events breakdownShow send counts and rates per sending domain, agent account, or recipient domain.](https://cli.nylas.com/docs/commands/deliverability-send-events-breakdown) ## Recommended guides [Track Email Opens, Clicks, and RepliesSend tracked email and receive open, click, and reply events over webhooks from the terminal. Verify the signatures, and learn why email open rates overcount.](https://cli.nylas.com/guides/track-email-opens-replies-cli) [SMTP Reply Codes ExplainedDecode SMTP reply codes: 2xx success, 4xx transient retry, 5xx permanent. Read bounce DSN enhanced codes and debug delivery from the terminal.](https://cli.nylas.com/guides/smtp-reply-codes-explained) [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.](https://cli.nylas.com/guides/email-bounce-codes-reference) [Validate Email Addresses from the CLIValidate 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.](https://cli.nylas.com/guides/email-address-validation-cli) [AI Agent Email Bounce Detection and RetryDeterministic 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.](https://cli.nylas.com/guides/ai-agent-email-bounce-retry) [Soft Bounce vs Hard Bounce ExplainedSoft 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.](https://cli.nylas.com/guides/soft-bounce-vs-hard-bounce) Run `nylas deliverability send-events list --help` for full help output.