buddyboss/manage-subscriptions manages what a member is subscribed to: forums, topics and groups whose activity sends them notifications.
user_id names whose subscriptions these are rather than defaulting to the account running the call.
At a glance
| Ability | buddyboss/manage-subscriptions |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Notifications & Invites |
| Requires | AcrossAI Pro, plus BuddyBoss Platform active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
That parameter is required for a reason that runs in both directions. Subscribing somebody signs them up for email they did not ask for; unsubscribing stops mail they may be relying on.
Neither is neutral, and defaulting to the caller’s own account would make it very easy to do one of them to the wrong person.
The email volume is the practical consideration. A subscription to a busy forum is a notification per reply, and somebody subscribed to several is receiving a great deal of mail attributable to a decision they did not make.
Unsubscribing has the quieter failure: a member relying on topic notifications to do their job stops receiving them and finds out by missing something.
action=list shows them, subscribe adds one, unsubscribe removes one.
Idempotent.
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. |
action | string | Yes | list, subscribe or unsubscribe. |
object_type | string | For the write actions | forum, topic or group. |
object_id | integer | For the write actions | Which one. |
What comes back
| Name | Type | What it is |
|---|---|---|
subscriptions | array | What they are subscribed to, for list. |
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 this member subscribed to?
It resolves to one call:
{
"ability": "buddyboss/manage-subscriptions",
"parameters": {
"user_id": 44,
"action": "list"
}
}Worth knowing
- Subscribing generates email the member did not ask for.
- Unsubscribing stops mail they may be relying on.
- The user ID is required so neither happens to the wrong person.
- A busy forum subscription is a notification per reply.
Related abilities
- BuddyBoss Get Account Settings — their notification preferences
- BuddyBoss List Notifications — what subscriptions produce
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category