The organization's notifications setup

GET /settings

The organization's notifications setup: the sender (the name its mail goes out under and its one accounts email, absent until saved — nothing is sent before), its own sending domain with the DNS records it needs and what the last lookup found, and the From address mail goes out from today — the accounts email once its domain is verified, else Manifold's sending address.

Access

Requires settings:read or notifications:read.

Any one of these scopes is enough.

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

AI agent tool

Agents call this as notifications_get_settings (Notifications: Senders and sending domain), in the notifications toolset. It only reads.

Connecting an agent: AI agents.

Example

curl

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

JavaScript (fetch)

const response = await fetch("https://notifications.getmanifold.io/settings", {
  method: "GET",
  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.

`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
`RequestLogUnavailable` tokenId, reason	The service could not record the request, so it did nothing.	Try again shortly.

How refusals work everywhere: Errors.

Used in

Send mail from your own domain, step 13: Read the settings