---
title: "Person Activity Monitoring: one page of monitored people"
method: GET
path: "/api/me/intelligence/monitoring"
tags: ["me", "intelligence"]
---

# Person Activity Monitoring: one page of monitored people

`GET /api/me/intelligence/monitoring`

## Request

- Base URL: `https://api.signalraven.ai`
- URL: `https://api.signalraven.ai/api/me/intelligence/monitoring`
- Auth: none declared

Ongoing monitoring of specific individuals (weekly check of their posts, reposts, comments and reactions through the person activity judge). Rows are target_person sources; they do not count against the plan source cap. Paged (2026-10-07): status filters active | inactive (ended or paused) | removed | all (default, active first); q searches display name, profile URL and the cached profile name, company and headline; total matches the filters while counts covers the whole workspace.

## Query parameters

- `status` 'active' | 'inactive' | 'removed' | 'all'
- `q` string
- `limit` integer
- `offset` integer

## Response `200`

Monitored people

- MonitoringListResponse
  - `people` MonitoredPersonRow[], required
    - `id` string, uuid, required
    - `linkedinUrl` string, required
    - `slug` string, required
    - `displayName` string, required
    - `isActive` boolean, required
    - `inactiveReason` string, nullable, required
    - `createdAt` string, date-time, required
    - `lastCheckedAt` string, date-time, nullable, required
    - `monitoring` object, nullable, required
      - `periodDays` union, required: 30, 90 or 180 days; null means forever.
        - 30
        - 90
        - 180
      - `startedAt` string, required
      - `until` string, nullable, required
      - `snapshotId` string
      - `skipInitialBackfill` boolean
      - `weekday` integer
      - `admitLevel` union: 2 (default): stated needs only — the person's activity becomes a signal when its text states a need, pain or buying moment your product addresses. 3: also topic interest — professional content about your category with no stated need, delivered as topic-interest signals with a lower strength floor (5 instead of 8).
        - 2
        - 3
      - `endsInDays` integer, nullable, required
      - `ended` boolean, required
    - `health` object, required
      - `status` string, nullable, required
      - `lastRunOutcome` string, nullable, required
      - `lastSuccessfulRunAt` string, nullable, required
      - `consecutiveFailedRuns` integer, required
    - `person` object, nullable, required
      - `fullName` string, nullable, required
      - `headline` string, nullable, required
      - `currentTitle` string, nullable, required
      - `currentCompany` string, nullable, required
    - `signals` object, required
      - `last30` integer, required
      - `last90` integer, required
      - `total` integer, required
    - `latestSnapshot` object, nullable, required
      - `id` string, uuid, required
      - `status` string, required
      - `createdAt` string, required
      - `readyAt` string, nullable, required
  - `total` integer, required
  - `limit` integer, required
  - `offset` integer, required
  - `counts` MonitoringCounts, required
    - `active` integer, required
    - `inactive` integer, required
    - `removed` integer, required
  - `activeCount` integer, required

## Other responses

- `400`: Invalid query
- `403`: Plan or role not allowed

---

[API](https://skmtc.dev/signalraven/apis/zygnal-api.md) · [All operations](https://skmtc.dev/signalraven/apis/zygnal-api/llms.txt) · [OpenAPI document](https://skmtc.dev/signalraven/apis/zygnal-api/revisions/36e1d9b9d604?raw)