Connection alerts

List the open broken-connection alerts of social publishing

social_planner.credential_alerts.list

Lists the organization's open publishing incidents caused by a broken network connection, one per network at most (instagram, facebook, linkedin, linkedin_profile, tiktok, twitter, google_business), most recently updated first: when a post fails because the network's connection expired or lacks a permission (reason credentials_expired or permissions_missing), every later post on that network will fail too, so MB Suite emails a «your next posts will also fail» notice at most once every 24 hours per network (last_alert_at) and keeps the incident here with first_detected_at, failed_post_count (posts that failed since then) and last_post_id (that post's publish jobs, with account_id and the network's error, are in social_planner.posts.jobs.list). An alert stays until a post publishes successfully on that network: reconnecting does not clear it, so it says «nothing went out on this network since the incident», not «the connection is broken now»; to know whether the connection works today, check integrations.credentials.list. An empty list means no open incident. Calls no network and returns no token or credential id. Requires view access to the Social Planner.

Scope

social_planner:read

Permission

View the module

MCP tool

social_planner_credential_alerts_listOn the full surface; on the compact one, mb_execute_operation with id: "social_planner.credential_alerts.list".

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

Parameters

No parameters.

Response

Errors

Example

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