The organization's brand

GET /settings/brand

The organization's brand: its business name, brand and accent colours (with the text colour its brand colour takes), how customers reach it, the footer and terms, and its logo — what every email template, customer page and PDF wears.

404 BrandNotFound until one is saved.

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_brand (Notifications: Brand), in the notifications toolset. It only reads.

Connecting an agent: AI agents.

Example

curl

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

JavaScript (fetch)

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

{
  "businessName": "Ridgeline Outdoor",
  "brandColour": "#1f4d3a",
  "accentColour": "#1f6f50",
  "contact": {
    "email": "accounts@ridgeline-outdoor.example",
    "phone": "+61 2 9000 1234",
    "website": "https://ridgeline-outdoor.example"
  },
  "footer": "Ridgeline Outdoor Pty Ltd · ABN 12 345 678 901",
  "terms": "Quotes hold their prices until the date shown. Payment within 30 days of invoice.",
  "onBrandColour": "#ffffff",
  "logo": {
    "reference": "brand-logo-2026-10",
    "contentType": "image/png",
    "size": 18204,
    "version": 1,
    "storedAt": "2026-10-20T05:12:00.000Z"
  }
}

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.

`404`

Refusal	What it means	What to do
`BrandNotFound`	No such record in this organization.	Check the id in the path or the body.

`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

Share a quote your customer can accept, step 2: Read it back