Webhooks & monitoring Beta

Continuous monitoring re-checks a token over time and notifies you when its risk profile changes. This capability is in active development.

Not yet delivering alerts. The deep-dive endpoint accepts enable_monitoring and webhook_url and echoes a monitoring object in its response, but outbound webhook delivery is not live. This page documents the planned contract so you can build against it early. Treat the schema as provisional.

Enabling monitoring

Monitoring is requested as part of a deep dive:

{
  "project_address": "0x…",
  "chain": "ethereum",
  "enable_monitoring": true,
  "monitoring_duration_days": 30,
  "webhook_url": "https://your-app.example.com/hooks/csds"
}

The response confirms the window:

{
  "monitoring": {
    "enabled": true,
    "monitoring_until": "2026-07-02T00:00:00Z",
    "alert_triggers": ["liquidity_removed", "ownership_transferred", "large_holder_dump"]
  }
}

Planned alert payload

When delivery ships, an alert POST to your webhook_url is expected to look like:

{
  "event": "risk_change",
  "project_address": "0x…",
  "chain": "ethereum",
  "previous_risk_score": 42,
  "current_risk_score": 88,
  "trigger": "liquidity_removed",
  "detected_at": "2026-06-15T09:30:00Z"
}

Planned delivery semantics

Signing: requests will carry a signature header so you can verify authenticity.
Retries: non-2xx responses will be retried with backoff.
Idempotency: each alert will include a stable id for dedupe.

Want to be notified when monitoring goes live? Keep an eye on the FAQ and the changelog.