Notifications API · settings

Start sending from the organization's own domain

POST /settings/domain

Start sending from the organization's own domain (ridgeline.com): Manifold registers the domain with its mail provider and answers the DNS records to create at the domain's DNS host — three DKIM CNAMEs, an MX and an SPF TXT on the bounce subdomain bounce.<domain>, and a DMARC TXT recommended where the domain has none.

Mail keeps going from Manifold's address until the records are found (POST /settings/domain/check). Appends notifications.sending-domain-added. 409 SendingDomainUnavailable for a domain another organization sends from or one of Manifold's own. Idempotent by state: adding the domain the organization already has answers it as it stands and appends nothing, and any other domain while one is held meets 409 SendingDomainExists — remove it first.

Access

Requires settings:write.

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

Retries

Idempotent by state: adding the domain the organization already has answers it as it stands and appends nothing, and any other domain while one is held meets 409 SendingDomainExists — remove it first.

Why every write carries a key: Idempotency and retries.

Facts appended

  • notifications.sending-domain-added

What a fact is: Facts and the journal.

AI agent tool

No agent tool. Sending from the merchant's own domain means records at their DNS host: the owner's work in Settings › Notifications, where the records are shown to copy.

Connecting an agent: AI agents.

Example

curl
curl -X POST 'https://notifications.getmanifold.io/settings/domain' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{
  "domain": "ridgeline-outdoor.example"
}'
JavaScript (fetch)
const response = await fetch("https://notifications.getmanifold.io/settings/domain", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.MANIFOLD_TOKEN}`, "Content-Type": "application/json" },
  body: JSON.stringify({
    "domain": "ridgeline-outdoor.example"
  }),
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const answer = await response.json();
Request body · application/json
{
  "domain": "ridgeline-outdoor.example"
}
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": "pending",
    "mailFromDomain": "bounce.ridgeline-outdoor.example",
    "records": [
      {
        "purpose": "dkim",
        "type": "CNAME",
        "name": "q3v7k2m9x4c8b1n6z5t0r2w8y4p7s3d1._domainkey.ridgeline-outdoor.example",
        "value": "q3v7k2m9x4c8b1n6z5t0r2w8y4p7s3d1.dkim.amazonses.com",
        "required": true,
        "state": "unchecked"
      },
      {
        "purpose": "dkim",
        "type": "CNAME",
        "name": "h8j2f6l0a4e9u3o7i1g5c2v8b6n0m4k7._domainkey.ridgeline-outdoor.example",
        "value": "h8j2f6l0a4e9u3o7i1g5c2v8b6n0m4k7.dkim.amazonses.com",
        "required": true,
        "state": "unchecked"
      },
      {
        "purpose": "dkim",
        "type": "CNAME",
        "name": "t5r1y9w3q7e2u6i0o4p8a3s7d1f5g9h2._domainkey.ridgeline-outdoor.example",
        "value": "t5r1y9w3q7e2u6i0o4p8a3s7d1f5g9h2.dkim.amazonses.com",
        "required": true,
        "state": "unchecked"
      },
      {
        "purpose": "mail-from-mx",
        "type": "MX",
        "name": "bounce.ridgeline-outdoor.example",
        "value": "10 feedback-smtp.ap-southeast-2.amazonses.com",
        "required": true,
        "state": "unchecked"
      },
      {
        "purpose": "mail-from-spf",
        "type": "TXT",
        "name": "bounce.ridgeline-outdoor.example",
        "value": "v=spf1 include:amazonses.com ~all",
        "required": true,
        "state": "unchecked"
      },
      {
        "purpose": "dmarc",
        "type": "TXT",
        "name": "_dmarc.ridgeline-outdoor.example",
        "value": "v=DMARC1; p=none;",
        "required": false,
        "state": "unchecked"
      }
    ],
    "addedAt": "2026-10-20T05:12:40.000Z"
  },
  "tracking": true,
  "fromAddress": "\"Ridgeline Outdoor\" <notifications@send.getmanifold.io>",
  "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

RefusalWhat it meansWhat 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

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

403

RefusalWhat it meansWhat 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.

409

RefusalWhat it meansWhat to do
SendingDomainExists domain The organization already sends from another domain.Remove that domain first.
SendingDomainUnavailable domain, reason Another organization sends from this domain, or it is one of Manifold's own.Use a domain you own.
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

RefusalWhat it meansWhat 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