---
title: "List lead activity"
method: GET
path: "/v1/leads/activityFeed"
tags: ["leads"]
---

# List lead activity

`GET /v1/leads/activityFeed`

## Request

- Base URL: `https://api.zevari.ai`
- URL: `https://api.zevari.ai/v1/leads/activityFeed`
- Auth: HTTP bearer

Transport: call this endpoint with HTTP GET and query parameters. Outbound activity for this workspace — what we actually did (LinkedIn messages, invites, reactions, comments, posts, profile views, and email sends) from action_receipts, across channels, with action type, status, account, and time-range filters plus cursor pagination. Profile views dominate this history by volume, so pass action_type when the user asks about sends, replies, or engagement specifically. Use actions_list_for_lead for one person and actions_get_receipt for one action. Does not include inbound comments or DMs received. Planned campaign steps carry written_by (who composed the words: your_ai, zevari, or together) and sent_by: zevari. Zevari delivers every campaign message; delivery is not authorship.

## Query parameters

- `action_type` union: Filter by action type, e.g. linkedin_send_message or linkedin_react_to_post. Accepts one value or a list.
  - string
  - string[]
- `status` union: Filter by receipt status: queued, executing, succeeded, failed, deferred, rejected, cancelled, outcome_unknown.
  - string
  - string[]
- `linkedin_account_id` string: Narrow to one LinkedIn sender account, or "active" for this session's account. Omit to see every channel; passing an account EXCLUDES email sends, which have no LinkedIn account. Re-pass unchanged on continuation pages.
- `from` string: ISO-8601 lower bound on occurred_at (first page only)
- `to` string: ISO-8601 upper bound on occurred_at (first page only)
- `cursor` string: next_cursor from the previous page. Re-pass action_type/status unchanged; do not pass from/to.
- `limit` number: Max results

## Response `200`

Successful Zevari API response.

- ZevariResponseEnvelope
  - `ok` boolean, required: False when the underlying tool reports an error or a partial failure.
  - `method` string, required: Public API method name.
  - `data` unknown, required
  - `request_id` string, required: Request correlation ID. Also returned in X-Zevari-Request-Id.

## Other responses

- `400`: Invalid arguments or method execution error.
- `401`: Missing, invalid, expired, revoked, or unauthorized API key.
- `404`: Unknown or non-public Zevari API method.
- `429`: API key rate limit exceeded.
- `500`: Unhandled server error.

---

[API](https://skmtc.dev/zevari/apis/zevari-public-api.md) · [All operations](https://skmtc.dev/zevari/apis/zevari-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/zevari/apis/zevari-public-api/revisions/a0bc3afac227?raw)