Push a test to one of the caller's own devices

POST /me/push/devices/{deviceId}/test

Push a test to one of the caller's own devices, now — whatever kinds they switched off and whatever their quiet hours say, since they asked — to see that it arrives.

Appends notifications.requested, then notifications.sent or notifications.failed; a token the push service no longer knows also appends notifications.push-device-removed. 404 PushDeviceNotFound for a device that is not the caller's. Keyed on notificationId, the caller-minted ntf_ id: a retry answers the push as recorded and never pushes twice.

Access

Requires a signed-in session: a person's own devices and preferences: the route reads and changes only the caller's

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

Retries

Keyed on notificationId, the caller-minted ntf_ id: a retry answers the push as recorded and never pushes twice.

A retry with the same key answers 200, with what the first call recorded.

Why every write carries a key: Idempotency and retries.

Facts appended

notifications.requested
notifications.sent
notifications.failed
notifications.push-device-removed

What a fact is: Facts and the journal.

AI agent tool

No agent tool. A test push is how a person sees their own phone light up under Settings › Push notifications; there is nothing for an agent to see.

Connecting an agent: AI agents.

Example

curl

curl -X POST 'https://notifications.getmanifold.io/me/push/devices/pdv_01a15c20-4d5e-7f6a-8b9c-0d1e2f3a4b5c/test' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{
  "notificationId": "ntf_01a15c42-6f7a-7b8c-9d0e-1f2a3b4c5d6e"
}'

JavaScript (fetch)

const response = await fetch("https://notifications.getmanifold.io/me/push/devices/pdv_01a15c20-4d5e-7f6a-8b9c-0d1e2f3a4b5c/test", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.MANIFOLD_TOKEN}`, "Content-Type": "application/json" },
  body: JSON.stringify({
    "notificationId": "ntf_01a15c42-6f7a-7b8c-9d0e-1f2a3b4c5d6e"
  }),
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const answer = await response.json();

Request body · application/json

{
  "notificationId": "ntf_01a15c42-6f7a-7b8c-9d0e-1f2a3b4c5d6e"
}

Response · 200 · application/json

{
  "id": "ntf_01a15c42-6f7a-7b8c-9d0e-1f2a3b4c5d6e",
  "kind": "push-test",
  "channel": "push",
  "status": "sent",
  "to": [
    "pdv_01a15c20-4d5e-7f6a-8b9c-0d1e2f3a4b5c"
  ],
  "cc": [],
  "from": "Manifold",
  "subject": "Push works",
  "source": {
    "kind": "push-device",
    "id": "pdv_01a15c20-4d5e-7f6a-8b9c-0d1e2f3a4b5c"
  },
  "requestedBy": {
    "_tag": "user",
    "id": "usr_01a15709-7582-7646-b491-261a138f0650"
  },
  "requestedAt": "2026-10-29T01:13:00.000Z",
  "recipient": {
    "user": "usr_01a15709-7582-7646-b491-261a138f0650"
  },
  "push": {
    "body": "Notifications reach Sam's iPhone. Tap to open your devices.",
    "path": "/settings/push",
    "actions": []
  },
  "sentAt": "2026-10-29T01:13:01.000Z",
  "providerMessageId": "projects/manifold-508900/messages/0:1761700381000000%e2b7c1f9e2b7c1f9",
  "steps": [
    {
      "status": "requested",
      "at": "2026-10-29T01:13:00.000Z"
    },
    {
      "status": "sent",
      "at": "2026-10-29T01:13:01.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
`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.

`404`

Refusal	What it means	What to do
`PushDeviceNotFound` deviceId	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.	Send the same request again, with the same key.

How refusals work everywhere: Errors.