# List an account's verified recipients

Every outside address this account has asked to send to, pending or verified, oldest first. Addresses on the account's own domains are always verified recipients and are never listed. Unpaginated: an account holds at most 100. Reachable by the account's own key or a system key.

## `GET /api/v1/accounts/{accountId}/verified-recipients`

### Path parameters

- `accountId` (string, required) — Account ULID identifier

### Responses

**200** — The list

`application/json` → object

- `recipients` (VerifiedRecipient[], required)
  - `address` (string, required) — The address, normalized as forwarding destinations are: trimmed, lowercased, its domain in A-label form
  - `createdAt` (integer <int64>, required) — When the address was added, in epoch seconds
  - `id` (string, required) — Verified recipient ULID: the handle DELETE takes, so no address is path-encoded
  - `lastSentAt` (integer | null, required) — When a confirmation link was last mailed, in epoch seconds. Each link works for seven days from its own mailing; a pending address whose newest link has expired is dropped at the next add, and posting it again mails a fresh one
  - `state` ("pending" | "verified", required) — Confirmation state; only 'verified' counts as a verified recipient
  - `verifiedAt` (integer | null, required) — When its owner pressed Confirm, in epoch seconds, or null while pending

**401** — unauthorized: the bearer credential is missing, malformed, expired, or revoked. Carries a `WWW-Authenticate: Bearer` challenge

`application/json` → ErrorBody

**404** — not_found: the account does not exist or is not accessible to this principal

`application/json` → ErrorBody

**503** — temporary_failure: the platform's storage could not answer just now; retry after the Retry-After window. Any operation can answer this. A write that got it may have been applied, so retry it with the same idempotency key where it takes one, or read the state back first (see Transient failures in the API description)

`application/json` → ErrorBody

### Example request

```bash
curl -X GET 'https://api.open.email/api/v1/accounts/{accountId}/verified-recipients' \
  -H 'Authorization: Bearer oek_…'
```