The organization's own host for its customer pages

GET /settings/pages-domain

The organization's own host for its customer pages, when it has one: the subdomain, where it stands (pending, verified, live, lapsed), the DNS records to create and what the edge said is still missing — beside whether this deployment takes organizations' hosts at all, what the CNAME points at, and the origin the organization's customer links name today.

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

No agent tool. The customer pages' own host is DNS work the owner does with the records shown in Settings › Branding; links an agent sends already name whichever host is live.

Connecting an agent: AI agents.

Example

curl

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

JavaScript (fetch)

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

{
  "domain": {
    "id": "pgd_01a159a2-6c1e-7c0d-9a51-3f0e7d3b8a21",
    "hostname": "orders.ridgeline-outdoor.example",
    "status": "live",
    "records": [
      {
        "purpose": "route",
        "type": "CNAME",
        "name": "orders.ridgeline-outdoor.example",
        "value": "customers.getmanifold.io",
        "required": true
      },
      {
        "purpose": "ownership",
        "type": "TXT",
        "name": "_cf-custom-hostname.orders.ridgeline-outdoor.example",
        "value": "5cc07c04-ea62-4a5a-95f0-419334a875a4",
        "required": false
      }
    ],
    "edgeId": "0d89c70d-ad9f-4843-b99f-6cc0252067e9",
    "requestedAt": "2026-10-30T22:10:00.000Z",
    "problems": [],
    "verifiedAt": "2026-10-30T22:31:00.000Z",
    "liveAt": "2026-10-30T22:34:00.000Z",
    "checkedAt": "2026-10-30T22:34:00.000Z"
  },
  "available": true,
  "target": "customers.getmanifold.io",
  "origin": "https://orders.ridgeline-outdoor.example"
}

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

Serve your customer pages on your own domain, step 3: Read where it stands