Which operational emails reach the caller as one of the organization's owners or admins

GET /me/alert-preferences

Which operational emails reach the caller as one of the organization's owners or admins — an integration disconnected, the daily sync digest, a ledger that refused a journal, and billing's binding notices: each category on unless they switched it off, and mandatory for the ones that cannot be (billing).

403 PushNeedsPerson for any session that is not the person: an AI agent acting for them, an app, a background run, an impersonating administrator, a station.

Access

Requires a signed-in session: a person's own email alert switches: the route reads and changes only the caller's, and refuses any session that is not the person (an agent, an app, a background run, an impersonating administrator, a station)

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

AI agent tool

No agent tool. A person chooses which operational emails about the organization reach them under Settings › Email alerts; an agent has no inbox of its own to tune.

Connecting an agent: AI agents.

Example

curl

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

JavaScript (fetch)

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

{
  "categories": [
    {
      "category": "integrations",
      "enabled": true,
      "mandatory": false
    },
    {
      "category": "sync-problems",
      "enabled": false,
      "mandatory": false
    },
    {
      "category": "books",
      "enabled": true,
      "mandatory": false
    },
    {
      "category": "billing",
      "enabled": true,
      "mandatory": true
    }
  ]
}

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
`PushNeedsPerson` reason	The request was refused. `reason` says why.	The caller may not do this. Use a token whose roles allow it.
`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.