Skip to main content
POST
Test a notification

Authorizations

Authorization
string
header
required

Clerk API key. Create one in Settings → API Keys. Pass as Authorization: Bearer <key>. Keys carry a scope — read, write (implies read) or admin (implies write) — chosen when the key is minted. Each operation's security requirement (and its x-required-scope extension) names the minimum scope it needs; request the least-privileged key that covers the operations you call.

Path Parameters

id
integer
required
Required range: -9007199254740991 <= x <= 9007199254740991

Body

application/json

Optional body of a test delivery. An empty body delivers one mention.

limit
integer

How many of the feed's latest matching mentions to deliver to each destination (1–3, default 1).

Required range: 1 <= x <= 3
Example:

3

Response

200 response

Per-destination outcomes of a real test delivery of the latest matching mention(s).

notificationId
integer
required
Required range: -9007199254740991 <= x <= 9007199254740991
results
object[]
required

One entry per configured destination, in stored order.

mentions
object[]
required

The mentions that were delivered, newest first — the same set for every destination.