Stop sending from the organization's own domain

DELETE /settings/domain

Stop sending from the organization's own domain: the provider forgets it and mail goes from Manifold's address again; the DNS records can then be deleted at the DNS host.

Appends notifications.sending-domain-removed. Idempotent by state: a domain is removed once, and a retry meets 404 SendingDomainNotFound and appends nothing.

Access

Requires settings:write.

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

Retries

Idempotent by state: a domain is removed once, and a retry meets 404 SendingDomainNotFound and appends nothing.

Why every write carries a key: Idempotency and retries.

Facts appended

notifications.sending-domain-removed

What a fact is: Facts and the journal.

AI agent tool

No agent tool. Letting the sending domain go changes the address every customer sees mail from: the owner's call in Settings › Notifications.

Connecting an agent: AI agents.

Example

curl

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

JavaScript (fetch)

const response = await fetch("https://notifications.getmanifold.io/settings/domain", {
  method: "DELETE",
  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"
  },
  "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. Some can answer a retry of a call that already worked: they are marked.

`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 Can answer a retry	No such record in this organization.	If this answers a retry, your first call probably landed. Read the record before doing anything else.

`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 12: Let the domain go