Skip to main content
Every verdict is logged in Command. The Activity endpoints read that log for up to 30 days. Use them for nightly exports, threshold tuning, filters by agent or source, or copying verdicts into your own warehouse for longer retention.

Endpoints

List filters (repeatable where noted) match List Activity: List items include activity_id, occurred_at, event_name, status, source, provider, model, agent (id, name), rules (id, name, severity, type, policy), rule_count, and truncated_rule_count. The detail endpoint adds timeline and fuller rule fields. status maps to product outcomes: passed ≈ Pass, auto_fixed ≈ Fix, blocked ≈ Block, warned ≈ delivered with caution.

Nightly paginated export

Run once per night. Keep each request inside a 30-day window. Overlap the previous run (lookback) so records that appear after they occurred are not missed; dedupe by activity_id. Walk next_cursor until it is null. Encode cursor as a query value (--data-urlencode or an equivalent). Write CSV or NDJSON from the public list fields only.

Gotchas

  • 30 days. Ranges longer than 30 days return 400. Export nightly and keep your own copy for longer retention (Data Retention).
  • Lookback. Activity is eventually consistent. Overlap the previous window and dedupe by activity_id so late records are not dropped. If the overlap would exceed 30 days, clamp from to the cap.
  • Filters. Use only the documented list params above. Optional metadata on enforce is merged into the job; do not assume undocumented metadata keys are Activity filters.
  • Tune thresholds. Compare auto_fixed volume to human review outcomes; adjust the confidence threshold in Act on Each Verdict.

Next

Data Retention

How long ZeroDrift keeps content, verdicts, and activity records.

Act on Each Verdict

The Pass / Fix / Block / Escalate handler this export helps you tune.