> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leadinfo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> What the Leadinfo Data API covers, how it is organised, and how it relates to the Portal and the Leadinfo MCP.

The Leadinfo Data API gives you programmatic access to your Insights data: the companies identified on your tracked websites, their activity and firmographics, the tags and CRM links your team maintains, and the scores Leadinfo computes from all of that. The Portal, the public API and the [Leadinfo MCP](https://docs.leadinfo.com/product/mcp/overview.md) read the same data and apply the same rules.

## Base URL

```
https://data.leadinfo.com/v1
```

Every endpoint is versioned under `/v1/`. Trackers are addressed by their tracker code, the `LI-...` identifier of the tracking script on a website:

```
GET https://data.leadinfo.com/v1/trackers/LI-5A14070B93509/companies
```

## 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](https://docs.leadinfo.com/concepts/companies.md) and [Scoring](https://docs.leadinfo.com/concepts/scoring.md).

**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](https://docs.leadinfo.com/concepts/profiles.md).

**Traffic**: raw sessions with company, traffic source, landing page, pages and duration (`GET` and `POST /v1/trackers/{tracker_code}/sessions`). See [Marketing analytics](https://docs.leadinfo.com/guides/marketing-analytics.md).

**Signals**: identified visitors, form submissions and Leadbot conversations per tracker. See [People](https://docs.leadinfo.com/concepts/people.md).

## 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

| Property | Value |
| - | - |
| Version | `0.1.0` |
| Status | Public preview |
| Base URL | `https://data.leadinfo.com` |
| Path prefix | `/v1/` |

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

> [card] [Authentication](https://docs.leadinfo.com/authentication.md)
>
> Tokens, scopes and what a token acts for.

> [card] [Filters](https://docs.leadinfo.com/concepts/filters.md)
>
> The filter vocabulary behind company search, segments and profiles.

> [card] [Daily opportunities](https://docs.leadinfo.com/guides/daily-opportunities.md)
>
> Build a Sales action list with the best contact per company.

> [card] [Leadinfo MCP](https://docs.leadinfo.com/product/mcp/overview.md)
>
> Use the same data from Claude, ChatGPT or any MCP client.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.