Look the sending domain's records up now

POST /settings/domain/check

Look the sending domain's records up now: each record's state (found, missing, mismatch) from public DNS, and the provider's own verdict.

Appends notifications.sending-domain-verified when the provider has found the DKIM records, or notifications.sending-domain-failed when it has given up looking. Idempotent by state: a check that finds the domain where it already stands appends nothing. 404 SendingDomainNotFound when there is no domain.

Access

Requires settings:write.

How scopes come from roles: Scopes and roles. Getting a token: Authentication and app tokens.

Retries

Idempotent by state: a check that finds the domain where it already stands appends nothing.

Why every write carries a key: Idempotency and retries.

Facts appended

notifications.sending-domain-verified
notifications.sending-domain-failed

What a fact is: Facts and the journal.

AI agent tool

No agent tool. The domain is checked on an interval and from the settings panel; an agent reads where it stands with notifications_get_settings.

Connecting an agent: AI agents.

Example

curl

curl -X POST 'https://notifications.getmanifold.io/settings/domain/check' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN"

JavaScript (fetch)

const response = await fetch("https://notifications.getmanifold.io/settings/domain/check", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.MANIFOLD_TOKEN}` },
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const answer = await response.json();

Response · 200 · application/json

{
  "sender": {
    "senderName": "Ridgeline Outdoor",
    "accountsEmail": "accounts@ridgeline-outdoor.example"
  },
  "domain": {
    "id": "sdm_01a15777-5386-7d1f-af0c-8abfe9c68bf4",
    "domain": "ridgeline-outdoor.example",
    "status": "verified",
    "mailFromDomain": "bounce.ridgeline-outdoor.example",
    "records": [
      {
        "purpose": "dkim",
        "type": "CNAME",
        "name": "q3v7k2m9x4c8b1n6z5t0r2w8y4p7s3d1._domainkey.ridgeline-outdoor.example",
        "value": "q3v7k2m9x4c8b1n6z5t0r2w8y4p7s3d1.dkim.amazonses.com",
        "required": true,
        "state": "found"
      },
      {
        "purpose": "dkim",
        "type": "CNAME",
        "name": "h8j2f6l0a4e9u3o7i1g5c2v8b6n0m4k7._domainkey.ridgeline-outdoor.example",
        "value": "h8j2f6l0a4e9u3o7i1g5c2v8b6n0m4k7.dkim.amazonses.com",
        "required": true,
        "state": "found"
      },
      {
        "purpose": "dkim",
        "type": "CNAME",
        "name": "t5r1y9w3q7e2u6i0o4p8a3s7d1f5g9h2._domainkey.ridgeline-outdoor.example",
        "value": "t5r1y9w3q7e2u6i0o4p8a3s7d1f5g9h2.dkim.amazonses.com",
        "required": true,
        "state": "found"
      },
      {
        "purpose": "mail-from-mx",
        "type": "MX",
        "name": "bounce.ridgeline-outdoor.example",
        "value": "10 feedback-smtp.ap-southeast-2.amazonses.com",
        "required": true,
        "state": "found"
      },
      {
        "purpose": "mail-from-spf",
        "type": "TXT",
        "name": "bounce.ridgeline-outdoor.example",
        "value": "v=spf1 include:amazonses.com ~all",
        "required": true,
        "state": "found"
      },
      {
        "purpose": "dmarc",
        "type": "TXT",
        "name": "_dmarc.ridgeline-outdoor.example",
        "value": "v=DMARC1; p=none;",
        "required": false,
        "state": "found"
      }
    ],
    "addedAt": "2026-10-20T05:12:40.000Z",
    "verifiedAt": "2026-10-20T05:31:02.000Z",
    "checkedAt": "2026-10-20T05:31:02.000Z"
  },
  "tracking": true,
  "fromAddress": "\"Ridgeline Outdoor\" <accounts@ridgeline-outdoor.example>",
  "platformFromAddress": "notifications@send.getmanifold.io"
}

The panel writes this call in other languages. It does not send it: Manifold's APIs do not take calls from a web page on another site, so run the call from your own code or terminal. The whole API as OpenAPI: notifications-manager.openapi.json. Base URL https://notifications.getmanifold.io.

Errors

Every refusal is a status and a JSON body whose _tag names it. A refused call changes nothing.

`401`

Refusal	What it means	What to do
`Unauthorized` reason	The token is missing, expired or not one Manifold issued.	Get a fresh token and send the call again.
`TokenAlreadyUsed` tokenId	A single-use app token was already spent.	Mint a new token for this call.

`402`

Refusal	What it means	What to do
`SubscriptionRequired` status	The organization's subscription has lapsed, so writes are refused.	An owner settles billing. Reads still work meanwhile.

`403`

Refusal	What it means	What to do
`TenantRequired` userId	The token names no organization.	Choose the organization, then get a new token.
`ScopeRequired` required	The token's roles do not grant the scope this call needs.	Ask an owner or admin for a role that grants it.

`404`

Refusal	What it means	What to do
`SendingDomainNotFound` reason	There is no domain.	Check the id in the path or the body.

`409`

Refusal	What it means	What to do
`MirroredFromSource` source	This area is fed by your source system until the organization goes live.	Make the change in the source system, or go live first.

`503`

Refusal	What it means	What to do
`MailProviderUnavailable` reason	The mail provider did not answer, so nothing was sent.	Send the same request again shortly.
`RequestLogUnavailable` tokenId, reason	The service could not record the request, so it did nothing.	Send the same request again shortly.

How refusals work everywhere: Errors.

Used in

Send mail from your own domain, step 4: Check the records