---
title: Logs and exports
description: Find any email or API request, see what happened to it, and download your data as CSV.
---

Three tools help you answer "what happened to this?": the email list, the API request log, and CSV export.

## Emails

In the dashboard, **Emails** lists every email your team sent. Search by recipient, subject or email ID, and filter by status, API key, brand (sending domain), source (transactional or broadcast) and time range.

Open an email to see:

- its events in order: sent, delivered, delayed, bounced, opened, clicked and so on, with the reason for a delay or a bounce,
- the content as it was sent (preview, HTML or plain text) and its headers,
- for an email that has not gone out yet, why it is waiting (plan limit, warm-up, a safety check and so on),
- its [Deliverability Insights](/docs/concepts/deliverability-insights) score.

Through the API, `GET /emails` lists emails (newest first, with cursor pagination) and `GET /emails/{id}` returns one email with its last event. Both need a full-access API key. To get events pushed to you as they happen, use [webhooks](/docs/concepts/webhooks).

Email bodies and history are kept for 30 days on every plan, then removed.

## API request log

**Logs** in the dashboard lists every request made with your API keys or through MCP, for the last 30 days. Each row shows the status, method, path, the key or connected app that made it, and the time.

- Search by path, key or request ID. Filter by source (API key or MCP), by API key, by status class (`2xx`, `4xx`, `5xx`) and by time range.
- Open a row to see the request and response bodies. They help you find out why a call returned `422` or `403`.
- Bodies are stored only when they are JSON and under 64 KB. Email content (`html`, `text`) is replaced by its size, secrets such as tokens and passwords show as `[redacted]`, and headers are never stored.
- Only owners, admins and developers see the bodies.

## Export to CSV

Pages that list your data have an **Export CSV** button. The file carries the filters you have applied, so it matches what is on screen. An export holds at most 50,000 rows, newest first. It uses your dashboard sign-in, so there is no API endpoint for it.

What you can export depends on your [team role](/docs/team-roles):

| Export | Where | Roles |
| --- | --- | --- |
| Contacts, unsubscribes, broadcast recipients | Audience pages, and a broadcast's page | Owner, admin, marketing |
| Domains, API keys, API request log | Their own pages | Owner, admin, developer |
| Emails, suppression list, audit log | Emails, Audience → Suppressions, Settings | Owner, admin |

The request log export has the columns `request_id`, `created_at`, `method`, `path`, `status`, `duration_ms` and `caller`. The contacts export includes an `unsubscribed` column and an `unsubscribed_domains` column (`*` means the whole team).

## Erasing a person's data

To remove a recipient from your history, delete the contact with `erase: true`, as described in [Contacts](/docs/concepts/contacts). It also removes the address from email history, event payloads and API request logs.
