> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sequenzy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Receiving Domain

> Get a receiving domain's status and DNS records

Get one receiving domain: its status, the DNS records to publish and what to
fix. This reads the latest stored check. To check DNS now, use [Verify Receiving
Domain](./verify).

Requires the `websites:read` scope.

CLI: `sequenzy receiving-domains get support.acme.com`. MCP:
`get_receiving_domain`.

## Status

* **`verified`**: mail arrives, and new reply addresses for emails from all
  your sending domains use this domain. The first verification of a domain added
  with [Add Receiving Domain](./create) turns Inbox on.
* **`pending`**: waiting for the DNS records. A newly added name is reserved
  for your workspace for 7 days (`claimExpiresAt`). After that, another
  workspace may add it, which removes it from yours.
* **`failed`**: the domain was set up and something broke, such as a removed
  MX record, or its 7-day reservation ran out before the records were found.
  Mail that still arrives is accepted, but new reply addresses use
  `inbound.sequenzy.com` until it is fixed. `error` says what to change.

Sequenzy checks every receiving domain automatically: every 2 minutes for the
first hour after you add it, then every 15 minutes for the first day, then
hourly while it is pending. A verified domain is checked every 6 hours, and a
failed one starts with checks a minute apart that slow down to once a day the
longer it stays broken.

## Request

<ParamField path="domain" type="string" required>
  The receiving domain's name, such as `support.acme.com`, or its `id`.
</ParamField>

```bash theme={null}
curl "https://api.sequenzy.com/api/v1/receiving-domains/support.acme.com" \
  -H "Authorization: Bearer YOUR_API_KEY"
```

## Response fields

<ResponseField name="receivingDomain.id" type="string">
  Receiving domain ID.
</ResponseField>

<ResponseField name="receivingDomain.domain" type="string">
  The domain, lowercase without a trailing dot. Mail to any address on it
  reaches your Inbox.
</ResponseField>

<ResponseField name="receivingDomain.status" type="string">
  `pending`, `verified` or `failed`, as described above.
</ResponseField>

<ResponseField name="receivingDomain.records" type="object[]">
  DNS records to publish: `type` (`MX` or `TXT`), `name` (fully qualified),
  `value`, `priority` (MX only, `10`) and `status` (`pending`, `verified` or
  `misconfigured`). The MX record is always listed. The TXT record at
  `_amazonses.<domain>` is listed only when Amazon SES needs proof that you own
  the name, which is when no verified Amazon SES identity on the name or a
  parent domain already covers it. An MX record is `misconfigured` when the name
  also has MX records for another mail service.
</ResponseField>

<ResponseField name="receivingDomain.error" type="string | null">
  What to fix, when known. Always `null` while the domain is verified.
</ResponseField>

<ResponseField name="receivingDomain.claimExpiresAt" type="string | null">
  When a new domain that never verified stops being reserved for your workspace.
  `null` once it has verified, and for domains moved over from an earlier reply
  setup.
</ResponseField>

<ResponseField name="receivingDomain.verifiedAt" type="string | null">
  When the domain first verified.
</ResponseField>

<ResponseField name="receivingDomain.lastCheckedAt" type="string | null">
  When the domain was last checked.
</ResponseField>

<ResponseField name="receivingDomain.createdAt" type="string">
  When the domain was added.
</ResponseField>

## Responses

<ResponseExample>
  ```json 200 theme={null}
  {
    "success": true,
    "receivingDomain": {
      "id": "k3x9rd2m8q1pz7w4v6n0b5c",
      "domain": "acme.com",
      "status": "pending",
      "records": [
        {
          "type": "MX",
          "name": "acme.com",
          "value": "inbound-smtp.us-east-1.amazonaws.com",
          "priority": 10,
          "status": "misconfigured"
        }
      ],
      "error": "acme.com also has MX records for Google Workspace, so mail would be split between them. Remove the other MX records, or receive on a subdomain such as support.acme.com.",
      "claimExpiresAt": "2026-10-17T09:00:00.000Z",
      "verifiedAt": null,
      "lastCheckedAt": "2026-10-10T09:30:00.000Z",
      "createdAt": "2026-10-10T09:00:00.000Z"
    }
  }
  ```

  ```json 401 theme={null}
  {
    "success": false,
    "error": "Unauthorized"
  }
  ```

  ```json 404 theme={null}
  {
    "error": "Receiving domain not found.",
    "code": "not_found"
  }
  ```
</ResponseExample>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.