---
title: "List receiving domains"
method: GET
path: "/receiving-domains"
tags: ["Receiving Domains"]
---

# List receiving domains

`GET /receiving-domains`

## Request

- Base URL: `https://api.sequenzy.com/api/v1`
- URL: `https://api.sequenzy.com/api/v1/receiving-domains`
- Auth: HTTP bearer

Lists the domains and subdomains whose mail reaches your Inbox, in alphabetical order, with their status and the DNS records to publish. A workspace has one receiving domain; workspaces that set up several before keep them, and replies then use the sender's own domain or one on the same root, else the oldest verified one. Requires the websites:read scope. Marketer personal API keys cannot use receiving domain endpoints.

## Response `200`

Receiving domains returned

- object
  - `success` boolean, required
  - `receivingDomains` ReceivingDomain[], required
    - `id` string, required
    - `domain` string, required: Lowercase domain name without a trailing dot.
    - `status` 'pending' | 'verified' | 'failed', required: verified: mail arrives and new reply addresses use the domain. pending: waiting for the DNS records; a newly added name stays reserved for your workspace for 7 days. failed: the domain was set up and something broke, or its 7-day reservation ran out before the records were found; mail that still arrives is accepted, and new reply addresses use inbound.sequenzy.com until it is fixed.
    - `records` ReceivingDomainDnsRecord[], required: DNS records to publish. Always the MX record; the TXT record at _amazonses.<domain> is listed only when Amazon SES needs proof that you own the name.
      - `type` 'MX' | 'TXT', required
      - `name` string, required: Fully qualified record name.
      - `value` string, required
      - `priority` integer: MX records only.
      - `status` 'pending' | 'verified' | 'misconfigured', required: misconfigured (MX only) means the name also has MX records for another mail service, which would split its mail.
    - `error` string, nullable, required: What to fix, when known. Always null while verified.
    - `claimExpiresAt` string, date-time, nullable, required: When a new domain that has never verified stops being reserved for your workspace, after which another workspace may add it. Null once verified, and for domains moved over from an earlier reply setup.
    - `verifiedAt` string, date-time, nullable, required: When the domain first verified.
    - `lastCheckedAt` string, date-time, nullable, required
    - `createdAt` string, date-time, required

## Other responses

- `401`: Unauthorized
- `403`: API key is missing the websites:read scope, or is a marketer personal key
- `503`: The database was temporarily unavailable. The request may be retried after the delay in Retry-After.

## Changes

- **2026-10-16** `db3873ca3d4d`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/sequenzy/apis/sequenzy-api/changes/receiving-domains/get.md)

---

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