Notifications API · alerts
Replace the operational-email categories the caller switched off
PUT /me/alert-preferences
Replace the operational-email categories the caller switched off (muted, every other on); a binding category (billing) cannot be listed.
Only the person sets them: 403 PushNeedsPerson for an AI agent acting for them (whatever it was granted), an app, a background run, an impersonating administrator or a station. Appends notifications.alert-preferences-saved. Idempotent by content: saving what is held appends nothing.
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.
Retries
Idempotent by content: saving what is held appends nothing.
Why every write carries a key: Idempotency and retries.
Facts appended
notifications.alert-preferences-saved
What a fact is: Facts and the journal.
AI agent tool
No agent tool. Which operational emails reach a person is that person's own choice under Settings › Email alerts, never an agent's.
Connecting an agent: AI agents.
Example
curl -X PUT 'https://notifications.getmanifold.io/me/alert-preferences' \
-H "Authorization: Bearer $MANIFOLD_TOKEN" \
-H 'Content-Type: application/json' \
-d '{
"muted": [
"sync-problems"
]
}'const response = await fetch("https://notifications.getmanifold.io/me/alert-preferences", {
method: "PUT",
headers: { Authorization: `Bearer ${process.env.MANIFOLD_TOKEN}`, "Content-Type": "application/json" },
body: JSON.stringify({
"muted": [
"sync-problems"
]
}),
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const answer = await response.json();{
"muted": [
"sync-problems"
]
}{
"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. | Send the same request again shortly. |
How refusals work everywhere: Errors.