Emails, domains & logs

The dashboard's monitoring views show what your integration has sent and let you debug it without adding logging of your own.

Emails

Emails lists every message on your account, newest first. Each row shows the recipient, subject, current status and time. When a message has been opened or clicked, the row shows Opened or Clicked (a click outranks an open) — engagement layered on top of the underlying delivery status.

Search and filter

Narrow the list by:

• Status — pick one or more; the list shows messages matching any of them. Includes Opened, Clicked and Delivery delayed alongside the delivery outcomes. Filtering Opened returns opened-but-not-clicked messages, matching what the row shows.
• Date range — preset shortcuts (Today, Yesterday, Last 7 / 15 / 30 / 90 days) or a custom range picked on the calendar (bounded to the last 90 days).
• Recipient or subject — free-text search.
• API key — the key a message was sent with.

Use it to answer questions like "did the receipt for this customer go out?" or "what bounced yesterday?".

Message detail

Click any row to open the message. The detail view shows:

• The full headers — from, to, reply_to, subject.
• The rendered HTML preview and the plain-text body.
• An event timeline — sent, delivered, bounced, complained, delivery delayed, plus any opens and clicks if tracking is on. Click any event to open a panel with the raw detail AWS reported — SMTP response, bounce diagnostic, the clicked URL, or the delay reason.

The message id shown here is the same UUID returned by POST /v1/emails and carried in webhook events.

Domains

Domains lists every sending domain with its region, verification status and creation date. Filter by status or region, search by name, and export the filtered list as CSV. From here you add domains, open a domain to publish DNS records and verify it, and configure open & click tracking.

Tick one or more rows to delete domains in bulk. Opening a domain shows a Records tab (the DNS to publish) and a Configuration tab (Return-Path, region, tracking and the delete action).

Full walkthrough: Domains & verification.

Request logs

Logs records every API request your application makes to SendGrail — the single most useful view when an integration misbehaves.

Each entry captures:

• Method and path — e.g. POST /v1/emails.
• Status code and latency.
• The request body your app sent and the response body SendGrail returned.
• Timestamp and the API key used.

When a send doesn't do what you expect, open the log entry for that request: the response body shows the exact 422 validation message or error SendGrail sent back, so you can see what your code actually submitted versus what you intended.

Logs can be filtered by status code and path, which makes it easy to pull up, say, every 4xx from the last day.