The organization's own email templates

GET /email-templates

The organization's own email templates, most recently saved first, each at its latest version with its whole source, its kind, the starter it was made from and whether its kind renders it (active).

Archived templates are left out unless archived=true.

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_list_email_templates (Notifications: List email templates), in the notifications toolset. It only reads.

Connecting an agent: AI agents.

Example

curl

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

JavaScript (fetch)

const response = await fetch("https://notifications.getmanifold.io/email-templates", {
  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": "etp_01a15a02-7c41-7a6e-9d10-3f6c2b8e4a11",
      "kind": "invoice",
      "name": "Invoice — our colours",
      "source": "import { Container, Heading, Text, money } from \"@manifold/email\";\nexport const subject = (data) => `Invoice ${data.invoice.number} from ${data.shop.name}`;\nexport default function Invoice(data) {\n  return (\n    <Container>\n      <Heading>Thanks, {data.customer?.firstName ?? \"there\"}</Heading>\n      <Text>{money(data.invoice.totals.totalCents, data.invoice.currency)} is due.</Text>\n    </Container>\n  );\n}\n",
      "version": 2,
      "basedOn": "invoice-classic",
      "active": true,
      "archived": false,
      "createdAt": "2026-10-27T02:10:00.000Z",
      "savedAt": "2026-10-27T02:14:31.000Z",
      "savedBy": {
        "_tag": "user",
        "id": "usr_01a15709-7582-7646-b491-261a138f0650"
      }
    }
  ]
}

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

Design your own emails, step 9: List your templates