The notification log

GET /notifications

The notification log, newest first: every message sent for the organization, by email or text — what it was, why (the record it is about), to whom, from which address or sender ID, who asked, when, and what became of it.

Narrow by status, kind, channel, sourceId (everything sent about one order or purchase order) or to (one email address or phone number). At most limit a page (default 50, capped at 200); pass the page's next back as before for the older ones.

Access

Requires notifications:read.

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

AI agent tool

Agents call this as notifications_list_notifications (Notifications: List notifications), in the notifications toolset. It only reads.

Connecting an agent: AI agents.

Example

curl

curl -X GET 'https://notifications.getmanifold.io/notifications?to=ops%40ridgeline-outdoor.example&limit=50' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN"

JavaScript (fetch)

const response = await fetch("https://notifications.getmanifold.io/notifications?to=ops%40ridgeline-outdoor.example&limit=50", {
  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

{
  "items": [
    {
      "id": "ntf_01a157ae-4288-7f3b-bb14-41f2affd24eb",
      "kind": "sending-test",
      "channel": "email",
      "status": "sent",
      "to": [
        "ops@ridgeline-outdoor.example"
      ],
      "cc": [],
      "from": "\"Ridgeline Outdoor\" <accounts@ridgeline-outdoor.example>",
      "replyTo": "accounts@ridgeline-outdoor.example",
      "subject": "Test message from Ridgeline Outdoor",
      "source": {
        "kind": "settings",
        "id": "sender"
      },
      "requestedBy": {
        "_tag": "user",
        "id": "usr_01a15709-7582-7646-b491-261a138f0650"
      },
      "requestedAt": "2026-10-20T05:40:11.000Z",
      "sentAt": "2026-10-20T05:40:12.000Z",
      "providerMessageId": "0108019a2b3c4d5e-01a1587e-cd9b-7f2a-9b3c-4d5e6f7a8b9c-000000",
      "steps": [
        {
          "status": "requested",
          "at": "2026-10-20T05:40:11.000Z"
        },
        {
          "status": "sent",
          "at": "2026-10-20T05:40:12.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.

`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

Send mail from your own domain, step 7: Read the log
Send text messages under your own name, step 5: Read the texts in the log