Menu

API reference · Alerts

Platform accounts

alerts · target_platforms · 1 operation

GET/v1/alerts/target-platforms

List the platform accounts an alert can watch

alerts.target_platforms.list

ReadIdempotentSince 2026-11-01

Lists the platforms connected to the workspace or to one of its Accounts (target_org_id, default the workspace) that an alert can watch, each with its accounts: platform (google_ads, meta_ads, tiktok_ads, linkedin_ads, google_analytics, google_search_console, google_business_profile, facebook_page, instagram, linkedin_page, youtube, tiktok), platform_label and accounts (account_id, account_name). Use a platform and one of its account_ids in alerts.alerts.create. Reads only MB Suite (nothing is fetched from the platforms). Not paginated. 400 invalid_target when the organization is not this workspace or one of its Accounts the credential reaches. With Google Ads, Google Business Profile, LinkedIn, TikTok or YouTube, their terms limit it through the API and the MCP: what they do not allow answers 403 platform_terms_restricted, and their records are left out of the response (the permissions guide lists what each platform allows).

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

Declared cost: up to 2 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>

The connected platforms and their accounts.

Errors

Example

curl "https://api.mb-suite.com/v1/alerts/target-platforms" \
  -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/target-platforms" \
  -H "Authorization: Bearer $MB_TEST_KEY"