RevnuDocs
Browse the Docs▾

API Reference / Get a lead

Get a lead

GET/api/v1/leads/{id}

One lead with its contacts, the surfaced draft, and the research behind each column.

Last updated

curl -H "Authorization: Bearer $REVNU_API_TOKEN" https://revnu.com/api/v1/leads/sn7…

Response

{ "lead": { …, fields, draft, research, contacts: [contact, …], contactsTruncated: false } }. Contacts are capped at 50, with contactsTruncated: true when there were more. The lead and each contact carry workflowRunId, the workflow run that created it, or null. 404 for an unknown or another account's lead.

draft is the surfaced draft, { subject, body } (each cut at 16,000 characters), or null when there is none. research is a list of entries, one per key the agent saved research under: { key, reasoning, sources: [{ url, title }], sourcesTruncated }, the agent's reasoning (cut at 8,000 characters) and up to 20 sources behind that value. A source whose URL is longer than 2,048 characters is left out rather than cut, and sourcesTruncated says when anything was left out. Keys with no visible column appear here too.

Agents: this page is also markdown at /docs/lead.md, answers Accept: text/markdown, and is listed in /docs/llms.txt.

Frequently Asked Questions

Each recommended lead is a row. List leads and take the id, then read the lead: `fields` has the fit and the Slack card reference where those columns are set up, `contact` is the person, `draft` or a `research` entry holds the message, and each research entry's `sources` has the links. The lead id is the stable id to track state against.