Developer Tools

Build with AnomalyArmor

REST API, CLI, and Python SDK for full programmatic access. Integrate data quality monitoring into your existing workflows however you prefer.

Get StartedView Docs
# gate pipeline on data quality
from anomalyarmor import Client
client = Client()
fresh = client.freshness.summary()
schema = client.schema.summary()
if fresh.stale_count == 0 and schema.critical_count == 0:
    run_airflow_task("build_report")
else:
    alert_oncall(fresh.stale_count, schema.critical_count)

Three Ways to Integrate

Choose the interface that fits your workflow

REST API

Full programmatic access to all AnomalyArmor features. Query freshness, schema changes, and anomalies. Manage tables and alerts programmatically.

Best for:
  • Custom dashboards
  • Automation workflows
  • Third-party integrations
API Reference

CLI

Run data quality checks from your terminal or CI/CD pipeline. Exit codes and JSON output for easy scripting and automation.

Best for:
  • CI/CD pipelines
  • Local development
  • Shell scripts
CLI Docs

Python SDK

Type-safe Python client with async support. Native integration with your Python data pipelines and orchestration tools.

Best for:
  • Airflow/Dagster tasks
  • Custom Python scripts
  • Data applications
SDK Docs

Use Cases

CI/CD

Pipeline Gates

Block deployments when data quality checks fail. Run freshness and schema checks as part of your CI pipeline before promoting to production.

Automation

Custom Alerting

Build custom alert routing beyond Slack and PagerDuty. Route alerts to internal tools, create tickets, or trigger custom remediation workflows.

Onboarding

Bulk Table Setup

Programmatically onboard hundreds of tables with consistent configurations. Define monitoring rules in code and version control your setup.

Ready to build?

Get your API key and start integrating in minutes.

Get StartedView Docs

Frequently Asked Questions

A REST API (OpenAPI-documented), a Python SDK (`pip install anomalyarmor`), and a CLI (`armor`). All three hit the same backend with the same API keys. Most teams use the SDK in notebooks and CI, the CLI for operator tasks, and the REST API for custom integrations.