---
title: "List a validation run's results"
method: GET
path: "/api/v1/validation-runs/{id}/results"
tags: ["Validation"]
---

# List a validation run's results

`GET /api/v1/validation-runs/{id}/results`

## Request

- Base URL: `https://api.sendly.now`
- URL: `https://api.sendly.now/api/v1/validation-runs/{id}/results`
- Auth: one of:
  - HTTP bearer
  - API key in cookie `better-auth.session_token`
  - OAuth 2 (authorization code, authorization URL `https://app.sendly.now/api/auth/oauth2/authorize`, token URL `https://app.sendly.now/api/auth/oauth2/token`, scopes: `validation:read`)

One page of a run's verdicts, cursor-paginated. Filter with `verdict` — `undeliverable` is the page you want when you are about to act on the results.

No total is reported: a run over a large list holds millions of rows, and counting them on every page read is the query this design exists to avoid. The run's own counters carry the numbers worth having.

`contact_id` is the contact the address belonged to when it was checked, and it is null for a contact deleted since. The `email` is stored on the result rather than read through the contact, so a completed run reports what it actually checked even after the contact changed address.

Requires the `validation:read` scope — View your email validation runs and their results.

## Path parameters

- `id` string, uuid, required: Resource id.

## Query parameters

- `limit` integer
- `after` string: Opaque cursor from a previous response's `next_cursor`.
- `verdict` 'deliverable' | 'undeliverable' | 'risky' | 'unknown': Return only results with this verdict — `undeliverable` is the usual filter.

## Response `200`

One page of results

- EmailValidationResultListV1: One page of a run's results. No total — a run over a large list holds millions of rows, and the run's own counters are the numbers worth reading.
  - `data` object[], required
    - `email` string, required
    - `has_mx_records` boolean, required: The domain publishes MX records.
    - `is_disposable` boolean, required: A throwaway-inbox provider. The ONLY flag here that lowers the verdict.
    - `is_personal` boolean, required: A free/consumer provider (Gmail, Outlook). List-quality information, not a problem.
    - `is_role_address` boolean, required: The local part addresses a role (`support@`, `info@`), not a person. List-quality information: role mailboxes are deliverable and companies answer them.
    - `reasons` string[], required: Human-readable findings. Prose for a person to read — branch on `verdict`, never on these.
    - `verdict` 'deliverable' | 'undeliverable' | 'risky' | 'unknown', required: `deliverable`: the domain resolves and accepts mail, with no badness signal. `undeliverable`: the domain does not exist or publishes no MX records. `risky`: deliverable, but a throwaway-inbox provider — mailing it costs sender reputation. `unknown`: DNS did not answer in time, so this address was NOT checked. Ask again; never delete a contact on `unknown`.
    - `contact_id` string, nullable, required
  - `has_more` boolean, required
  - `next_cursor` string, nullable, required: Pass as `after` to fetch the next page. `null` on the last page.

## Other responses

- `401`: `invalid_api_key` or `invalid_session` — missing or invalid credentials.
- `403`: `scope_missing`, `project_access_denied`, or `project_disabled`.
- `404`: `resource_not_found` — no validation run with this id belongs to the authenticated project.
- `422`: `validation_error` — query, path, or body parameters did not match the schema.
- `429`: `rate_limited` — see `Retry-After` and the `RateLimit` headers.
- `500`: `internal_error`.

---

[API](https://skmtc.dev/sendly/apis/sendly-api.md) · [All operations](https://skmtc.dev/sendly/apis/sendly-api/llms.txt) · [OpenAPI document](https://skmtc.dev/sendly/apis/sendly-api/revisions/ce7cfb7f7c7e?raw)