Base URL
/v1/. Trackers are addressed by their tracker code, the LI-... identifier of the tracking script on a website:
Functional areas
Account:GET /v1/auth/me (who the token acts for), GET /v1/trackers, GET /v1/tags, GET /v1/segments. Everything is scoped to the caller’s company and, for partner accounts, to the companies they manage.
Companies and scoring: the account list for a tracker (GET and POST /v1/trackers/{tracker_code}/companies), the daily action list (/opportunities), per-company drill-downs (details, sessions, pages, contacts) and the score explanation (/companies/{company_id}/score). See Companies and Scoring.
Profiles: the scoring model with the active ICP Builder and Intent Builder profiles (/v1/scoring-model) and data-driven drafts of ICP, Intent and Persona profiles (/v1/profiles/{kind}/suggestions). Profiles are saved in the Portal or through the Leadinfo MCP. See Profiles.
Traffic: raw sessions with company, traffic source, landing page, pages and duration (GET and POST /v1/trackers/{tracker_code}/sessions). See Marketing analytics.
Signals: identified visitors, form submissions and Leadbot conversations per tracker. See People.
What is not on the public API
IP identification (/identify), company and contact enrichment (/enrich, /discover) and the earlier /intent endpoints are not available on the public API at the moment. Older documentation and client code that references them should be retired.
Versioning and stability
Public preview means response shapes can gain fields at any time and existing fields change only with notice. Read documented field names and ignore fields you do not know.
Where to go next
Authentication
Tokens, scopes and what a token acts for.
Filters
The filter vocabulary behind company search, segments and profiles.
Daily opportunities
Build a Sales action list with the best contact per company.
Leadinfo MCP
Use the same data from Claude, ChatGPT or any MCP client.
