Kindly fill up the following to try out our sandbox experience. We will get back to you at the earliest.
Announcing Monitors API: Programmatic Monitoring & Alerts
The new Monitors API lets you programmatically manage data monitors and alerts, making it easier to integrate monitoring into your workflows and automate responses to data issues. The API provides endpoints to find, inspect, control, and trigger monitors on-demand.

We’re excited to release the new Monitors API — a set of endpoints that let you discover, inspect, control, and trigger data monitors programmatically. This makes it simple to integrate monitoring and alerting into orchestration, CI/CD, and observability workflows so teams can react faster and automate responses to data issues.
What’s New: Monitors API
The Monitors API provides the building blocks to manage monitor discovery, execution, and results retrieval across assets and tenants.
Key Features:
POST /monitors/search
— Find monitors for an asset, team, or tenant and list available on‑demand monitors.GET /monitors?monitor_id={id}
— Retrieve a monitor’s configuration, metadata, and latest run summary.GET /monitors/{monitor_id}/history
— Download historical scan results for reporting and analysis.POST /monitors/enable-disable
— Enable or disable scheduled monitors (useful for maintenance windows).POST /monitors/trigger
— Trigger one or more monitors on demand (useful after upstream jobs complete).GET /monitors/{monitor_id}/status
— Poll for quick status (running, completed, errored) without fetching full history.
Example Workflows
1. Discover & Visualize Monitors
- An external UI or orchestration tool calls
POST /monitors/search
for anasset_id
or tenant scope. - Display available scheduled and on‑demand monitors to users (name, type, severity, last run).
- Use
GET /monitors?monitor_id={id}
to show full configuration and latest execution summary.
2. Trigger On‑Demand Monitors After Upstream Changes
- Upstream ETL or deployment emits an event after data load/transform.
- Integration calls
POST /monitors/trigger
with monitor ids or asset id to run relevant monitors immediately. - Poll
GET /monitors/{monitor_id}/status
until runs complete, then fetchGET /monitors/{monitor_id}/history
for details. - Surface failures to alerting or orchestration systems for automated remediation or retries.
3. Temporarily Pause Scheduled Monitors for Maintenance
- Schedule a maintenance window or detect noisy false positives.
- Call
POST /monitors/enable-disable
to disable the scheduled monitor. - Re-enable when maintenance completes and verify via
GET /monitors?monitor_id={id}
.
4. Audit, Reporting & SLA Measurement
- Periodic job calls
POST /monitors/search
to enumerate monitors by tenant or team. - For each monitor, call
GET /monitors/{monitor_id}/history
to collect run results and incident counts. - Aggregate results for dashboards, compliance reports, or SLA tracking.
Getting Started
Head to the Public API docs to see full request/response examples and authorization details:
Looking Ahead
We’re rolling out APIs that will let customers programmatically create, update, schedule, and group monitors. This will enable use cases like provisioning monitors as part of CI/CD pipelines, creating tenant-specific monitor bundles, or automating temporary on‑demand checks during data deployments.
We’re excited to see how you integrate monitors into your workflows — from automated remediation to operational dashboards. If you have feedback or feature requests, please share them with the product team at product@decube.io.