# Email events in Application Logs and the Backend API

Email events (`email.*`) are now part of [**Application Logs**](https://clerk.com/docs/guides/dashboard/logs/application-logs.md). You can fetch them with the `GET /v1/logs` endpoint of the [Backend API](https://clerk.com/docs/reference/backend-api/tag/logs). Set `type` to `email.*` and `payload_filter[recipient_email]` to an address to find that recipient's emails. Call the endpoint from your own code or an AI agent to check whether a specific email was delivered to the recipient's mail server.

The **Application Logs** page in the Dashboard shows email events alongside every other event type, so the unfiltered feed puts a sign-up and its verification email in one timeline.

The [**Email Logs**](https://clerk.com/docs/guides/dashboard/logs/email-logs.md) page still shows them, with three changes:

- Recipient, IP address, and message ID filters match exactly instead of by substring.
- Blocked sends appear as **Bounced** or **Failed**.
- **Message ID** shows the Clerk email ID when one is available.

Email events go back to October 5, 2026, or as far as your plan's [retention period](https://clerk.com/docs/guides/dashboard/logs/overview.md#plans-and-retention) allows.

Read the [list of supported events](https://clerk.com/docs/guides/dashboard/logs/application-logs.md#supported-events) to learn more.