Notifications API · brands

The organization whose customer pages a host serves

GET /pages-hosts/{hostname}

The organization whose customer pages a host serves: what the customer pages service asks of a request that arrives on a host other than Manifold's own.

Answers a live host, and a lapsed one (which the pages send to Manifold's host); 404 PagesHostNotFound for any other — never requested, still pending, or removed. Appends nothing.

Access

Public: which tenant a live host serves is what its DNS already says publicly, and it names no record

No token: the link, the claim or the first message is the credential, as the description says.

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

AI agent tool

No agent tool. Which tenant a host serves is what the customer pages service asks of a request on a tenant's own host; an agent acts inside its own organization and never resolves hosts.

Connecting an agent: AI agents.

Example

curl -X GET 'https://notifications.getmanifold.io/pages-hosts/orders.ridgeline-outdoor.example'

const response = await fetch("https://notifications.getmanifold.io/pages-hosts/orders.ridgeline-outdoor.example", {
  method: "GET",
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const answer = await response.json();

{
  "hostname": "orders.ridgeline-outdoor.example",
  "tenantId": "org_01a156d2-8680-7738-ab2e-ff985e454887",
  "status": "live"
}

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.

404

How refusals work everywhere: Errors.

Used in

• Serve your customer pages on your own domain, step 5: Whose pages the host serves