Menu

API reference · Alerts

Recipients

alerts · recipients · 1 operation

GET/v1/alerts/recipients

List who can receive an alert

alerts.recipients.list

ReadIdempotentSince 2026-11-01

Lists the members who can receive an alert that watches the workspace itself or one of its Accounts (target_org_id, default the workspace): for an Account, the workspace's owners and admins, the Account's own members and the workspace members assigned to it; for the workspace, all its members. Members without a valid email are left out. Returns user_id, display_name (null when the member has no name), email, role and photo_url; pass the user_ids as recipients to alerts.alerts.create or alerts.alerts.update. Not paginated. 400 invalid_target when the organization is not this workspace or one of its Accounts the credential reaches.

Scope
alerts:read
Permission
View the module
MCP tool
alerts_recipients_listOn the full surface; on the compact one, mb_execute_operation with id: "alerts.recipients.list".

Declared cost: up to 60 reads and 0 writes per call (they count against the daily quota).

Parameters

target_org_idstringqueryoptional

The watched organization: the workspace (default) or one of its Accounts.

Response

dataarray<object>

Everyone who can receive the alert.

Errors

Example

curl "https://api.mb-suite.com/v1/alerts/recipients" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl "https://api.mb-suite.com/v1/alerts/recipients" \
  -H "Authorization: Bearer $MB_TEST_KEY"