> ## 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.

# Verify Receiving Domain

> Check a receiving domain's DNS records now

Check a receiving domain's DNS records and Amazon SES setup now instead of
waiting for the next automatic check, and get the result. Call it after you
publish or change the records. The request succeeds whatever the outcome; read
`status` and `error` for the result.

When the MX record points only to Sequenzy and Amazon SES confirms you own the
name, the domain becomes `verified`. If Sequenzy can't finish setting up
receiving on its side, the domain stays `pending` (or becomes `failed` if it
was verified before) with an `error`, and Sequenzy keeps retrying. When DNS or
Amazon SES gives no answer, the status is left unchanged and the next
automatic check runs 15 minutes later.

The first time a receiving domain you added with [Add Receiving
Domain](./create) becomes `verified`, Inbox turns on for your workspace
(`replyTrackingEnabled` on the company becomes `true`), and replies to emails
from all your sending domains start using it. Later checks leave the Inbox
setting as you set it. Receiving domains moved from an older reply setup, or
added by naming a sending domain in [Update Inbox
Address](../conversations/update-inbox-address), never change the Inbox
setting when they verify.

Requires the `websites:write` scope and owner or admin access.

CLI: `sequenzy receiving-domains verify support.acme.com`. MCP:
`verify_receiving_domain`.

## 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 -X POST "https://api.sequenzy.com/api/v1/receiving-domains/support.acme.com/verify" \
  -H "Authorization: Bearer YOUR_API_KEY"
```

## Response fields

<ResponseField name="receivingDomain" type="object">
  The receiving domain after the check, with the fields described in [Get
  Receiving Domain](./get).
</ResponseField>

## Responses

<ResponseExample>
  ```json 200 theme={null}
  {
    "success": true,
    "receivingDomain": {
      "id": "k3x9rd2m8q1pz7w4v6n0b5c",
      "domain": "support.acme.com",
      "status": "pending",
      "records": [
        {
          "type": "MX",
          "name": "support.acme.com",
          "value": "inbound-smtp.us-east-1.amazonaws.com",
          "priority": 10,
          "status": "verified"
        },
        {
          "type": "TXT",
          "name": "_amazonses.support.acme.com",
          "value": "pmBGN/7MjnfhTKUZ06Enqq1PeGUaOkw8lGhcfwefcHU=",
          "status": "pending"
        }
      ],
      "error": "Add the TXT record so Amazon SES can confirm you own support.acme.com.",
      "claimExpiresAt": "2026-10-17T09:00:00.000Z",
      "verifiedAt": null,
      "lastCheckedAt": "2026-10-10T09:10:00.000Z",
      "createdAt": "2026-10-10T09:00:00.000Z"
    }
  }
  ```

  ```json 403 theme={null}
  {
    "error": "You have view-only access to this company. Contact the owner to request edit permissions."
  }
  ```

  ```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.