Histórico

List alert triggers

alerts.history.list

Lists the times alerts triggered, newest first, paginated by cursor (limit 50 by default, up to 200): the alert (alert_id, alert_name), the watched organization and platform account, the metric, current_value and previous_value with delta_absolute and delta_percent, the threshold and condition, the severity (info, warning or critical, by how far the change went past the threshold), the evaluated date ranges and the addresses the email went to (recipient_emails, email_sent). Filter by alert_id or by target_org_id (both: a filtered page is filled by reading further, up to 600 triggers per call). Entries of deleted alerts stay. Only the hourly evaluation writes here; reading sends nothing. 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).

Escopo

alerts:read

Permissão

Ver o módulo

Tool do MCP

alerts_history_listNa superfície completa; na compacta, mb_execute_operation com id: "alerts.history.list".

Custo declarado: até 601 leituras e 0 escritas por chamada (contam na cota diária).

Parâmetros

Resposta

Erros

Exemplo

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

Testar com a sua API key de teste

Com uma API key de teste o pedido vai sempre para a sua organização de prática: dados de exemplo que você pode reiniciar.

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