Continuum API
Sign inGet free access →
Monitoring

Verification is the first decision. Monitoring is the system behind it.

Continuum API keeps checking mailbox and domain health after the first API response so your records and workflows stay current.

Get free access →View webhooks

Status drift

Watch verified contacts shift from valid to risky or invalid.

Domain health

Detect MX instability, DNS changes, and catch-all behavior changes.

System sync

Push updated status into CRMs, outbound tools, and workflows automatically.

How it works

Five steps from POST /v1/monitoring to a webhook in your stack.

Continuous monitoring is a scheduled, auditable re-run of the same verification engine — with signed webhooks and safe defaults so it slots into production infrastructure.

  1. Step 01

    Register a monitor

    POST an email address or domain to /v1/monitoring with an interval — hourly, daily, or weekly. Register one at a time or in bulk.

  2. Step 02

    We re-run the full engine on schedule

    Every scheduled tick runs all 12 verification layers — MX, SMTP, disposable, role, catch-all, greylisting, SPF/DMARC, blacklist — exactly like the live API.

  3. Step 03

    Every check is recorded

    Each run is stored with timestamp, status, sub-status, and score. Read the full history via /v1/monitoring/{id}/history to see drift over time.

  4. Step 04

    Webhook on any status change

    When the status differs from the previous check, we POST a signed status_changed event to your endpoint so your CRM or outbound tool reacts automatically.

  5. Step 05

    Auto-pause on repeated failures

    If your webhook endpoint fails repeatedly, the monitor auto-pauses and surfaces the error in the dashboard — no runaway retries, no spam.

Create a monitorPOST /v1/monitoring
curl -X POST https://api.continuumapi.com/v1/monitoring \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "target": "alex@company.com",
    "type": "email",
    "interval": "daily",
    "webhookUrl": "https://yourapp.com/hooks/continuum"
  }'

Intervals: hourly, every_6h, daily, weekly. Monitor targets can be an individual email or an entire domain.

status_changed webhooksigned · retried
POST https://yourapp.com/hooks/continuum
X-Continuum-Signature: sha256=…

{
  "event": "status_changed",
  "monitorId": "mon_01HZK4E9…",
  "target": "alex@company.com",
  "type": "email",
  "previousStatus": "valid",
  "newStatus": "risky",
  "previousSubStatus": null,
  "newSubStatus": "mailbox_full",
  "score": 41,
  "checkedAt": "2026-07-12T09:14:22.000Z",
  "source": "scheduled",
  "apiVersion": "2"
}

Every webhook is HMAC-signed with your endpoint secret. Continuum retries on 5xx with backoff and auto-pauses the monitor after repeated failures.

What teams do with it

Monitoring solves the problems point-in-time verification can't.

Once verified data flows into production systems, the useful question stops being 'is this valid today' and starts being 'tell me the moment it changes'.

Keep the CRM clean, automatically

Sync status_changed events straight into HubSpot or Salesforce so stale contacts get flagged the day a mailbox goes cold — not the week after a bounce campaign.

Protect sender reputation

Suppress addresses that drift from valid to risky before your next batch runs. Bounce rates stay under provider thresholds without a manual list clean.

Catch a key account going dark

Monitor decision-makers on strategic deals. If a champion's mailbox stops accepting mail before a renewal call, you hear about it in a webhook — not from a silent pipeline.

Change detection

Track mailbox and domain drift with infrastructure-grade signals.

Continuum API monitors the conditions that make email health degrade over time, then pushes those changes into the systems teams already use.

Event

valid → risky

An inbox that was safe last week now shows elevated risk.

Event

domain health changed

MX instability appears on a domain linked to active pipeline contacts.

Event

catch-all detected

A previously standard domain starts routing all mail through catch-all behavior.

AI-assisted summaries

  • 3 contacts became risky after a domain configuration change.
  • This list shows increased mailbox risk across active pipeline records.
  • Recommended: reverify active leads before the next campaign launch.

Delivery into your stack

  • Webhook events for monitoring state changes.
  • CRM field syncs to keep enrichment and routing current.
  • Outbound list updates before launch windows and scheduled sends.
Monitoring runs continuously after the first verification.