Skip to main content
The Alerts API provides access to data quality alerts triggered by AnomalyArmor monitoring. Use it to query alert history, check active incidents, and integrate with your incident response workflows.

Endpoints

Get Alerts Summary

Returns aggregate alert statistics.

Response

List Alerts

Query Parameters

Response

List Alert Rules

Returns configured alert rules for your organization.

Response

Alert Types

Alert Statuses

Use Case: Incident Response

Build an incident response script:
Output:

Use Case: Slack Bot Integration

Post alerts to Slack:

Common Questions

How do I filter alerts by asset or type?

Combine asset_id, alert_type, and status query parameters on GET /api/v1/sdk/alerts. For example, ?status=triggered&alert_type=freshness returns only active freshness alerts. The since parameter accepts an ISO-8601 timestamp to bound history queries.

Can I acknowledge or resolve alerts through the API?

The read endpoints on this page cover history and summaries. For state transitions (acknowledge / resolve), use the per-alert endpoints documented in the TypeScript SDK reference (client.alerts.acknowledge, client.alerts.resolve) which post to /api/v1/alerts/{alert_id}/acknowledge and .../resolve.

What alert types does AnomalyArmor emit?

The API returns freshness, schema_change, row_count, null_percentage, and duplicate_keys. Each carries a details object with the relevant context (e.g. hours_stale, threshold_hours for freshness). Use alert_type to route to different Slack channels or PagerDuty services.