ReplySparrow Docs

Lead source agents

Get logs for a source agent

Retrieve the run logs of one source agent. Each log entry is one signal run (one signal checking one item: a company page, a topic…) and reports how many leads were found (total_leads) vs. how many ended up imported after scoring and filtering (leads_created). Use it to answer questions like "how many leads did this agent create last week?", "which signals produce the most leads?" or "did any of this agent's signals fail recently?". Optionally narrow the window with date_from / date_to (ISO 8601). Capped at the 100 most recent logs (newest first). Needs the campaigns:read scope.

gethttps://app.replysparrow.com/api/v1/agents/{id}/logs

Authorizations

Authorizationstringheaderrequired

Your API key from Settings → API, sent as Bearer <token>.

Path Parameters

idstringrequired

Agent id

Query Parameters

date_fromstring<date-time>

Only runs started at or after this ISO 8601 date or date-time (UTC)

date_tostring<date-time>

Only runs started at or before this ISO 8601 date-time; a bare date includes that whole day

Response

application/json

Up to 100 most recent log entries for the agent (newest first)

Get logs for a source agent
curl --request GET \  --url https://app.replysparrow.com/api/v1/agents/string/logs \  --header 'Authorization: Bearer <token>'
[  {    "id": "0f6b…",    "agent_id": "5b0f3c2e-8a8e-4bd1-9a51-6f1f3c0f2a10",    "leads_created": 3,    "total_leads": 41,    "created_at": "2026-10-24T08:00:12.000Z",    "error_message": null,    "signal_type": "competitor_engagement",    "signal_value": "https://www.linkedin.com/company/globex/"  }]