buddyboss/list-notifications returns a member’s notifications with their IDs, component, action, related item and read state.
user_id is required, and the default includes read notifications.
At a glance
| Ability | buddyboss/list-notifications |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Notifications & Invites |
| Requires | AcrossAI Pro, plus BuddyBoss Platform active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
BuddyBoss’s bare route returns unread notifications only. For a member who has read everything that returns nothing — which reads as somebody who was never notified of anything, rather than somebody who is up to date.
Those are opposite conclusions from the same empty response, so the default is changed here and both states are returned. Narrow with state=unread or state=read when you mean one.
The user ID is required for the same reason it is on messages: the underlying route would otherwise default to the administrator running the tool, returning their own notifications as though they were the member’s.
The component filter is useful on a busy community, where a member’s notification list is mostly one component — usually activity or messages — and the interesting ones are buried.
The ID is what buddyboss/manage-notification needs.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
user_id | integer | Yes | Whose record this is. Required rather than defaulting, so an administrator’s own account is never acted on by accident. |
state | string | No | read or unread. Both by default. |
component_name | string | No | Restrict to one component. |
per_page | integer | No | Rows per page. |
What comes back
| Name | Type | What it is |
|---|---|---|
notifications | array | Each notification with its ID, component, action, related item and read state. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
What has this member been notified about?
It resolves to one call:
{
"ability": "buddyboss/list-notifications",
"parameters": {
"user_id": 44
}
}Worth knowing
- Read and unread both, unlike the bare route.
- An empty unread-only response means caught up, not never notified.
- The user ID is required so an administrator’s own list is never returned instead.
- Read-only.
Related abilities
- BuddyBoss Manage Notification — change the state
- BuddyBoss Get Account Settings — why some notifications never arrive
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category