buddyboss/list-threads returns the message threads in one member’s mailbox, with each thread’s ID, participants, unread count, message count and latest excerpt.
user_id is required and names whose mailbox to open.
At a glance
| Ability | buddyboss/list-threads |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Messages |
| 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 has no site-wide message list. Without a user ID the underlying route returns the mailbox of whoever is making the call — which, for an administrator running a tool, is their own inbox returned as though it were the community’s.
That is a confidently wrong answer, so the parameter is required rather than defaulted.
Reading another member’s private correspondence is permitted here because administrators hold bp_moderate. It is still somebody’s private correspondence, and the response names every participant so it is clear whose messages were opened.
The message count per thread is worth reading before any deletion. A subject line says nothing about how much correspondence sits under it, and buddyboss/delete-thread confirms against that count.
Pass box=sentbox for what they sent, or type=unread to narrow.
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. |
box | string | No | inbox or sentbox. |
type | string | No | Narrow to unread. |
per_page | integer | No | Rows per page. |
What comes back
| Name | Type | What it is |
|---|---|---|
threads | array | Each thread with its ID, participants, unread count, message count and latest excerpt. |
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 is in this member’s inbox?
It resolves to one call:
{
"ability": "buddyboss/list-threads",
"parameters": {
"user_id": 44
}
}Worth knowing
- There is no site-wide message list. The user ID is required for that reason.
- This is private correspondence, readable because of
bp_moderate. - The message count is what a deletion confirms against.
- Read-only.
Related abilities
- BuddyBoss Get Message Thread — read one thread
- BuddyBoss Delete Message Thread — remove one from a mailbox
- BuddyBoss Manage Message Thread — change its state
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category