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

# Get analytics

> Read what the account has swept and owns, per niche and state.

Answers the account's lifetime footprint: for every niche it has scraped, per state, how many ZIP or postal codes were swept and how many leads it owns from there. A state can carry leads with no codes swept, because a search anchored on one code also returns its neighbours.

`GET https://api.leadity.io/v1/account/analytics`

- Scope: `read`
- Spends credits: no
- MCP tool: `get_analytics`

## Headers

- `Authorization`, string, required. Bearer, a space, then an API key: Bearer lk_api_... An MCP key is refused here with wrong_key_kind.

## Example request

```bash cURL
curl "https://api.leadity.io/v1/account/analytics" \
  -H "Authorization: Bearer $LEADITY_API_KEY"
```

```javascript Node.js
const response = await fetch("https://api.leadity.io/v1/account/analytics", {
  headers: {
    Authorization: `Bearer ${process.env.LEADITY_API_KEY}`,
  },
});

const data = await response.json();
console.log(data);
```

```python Python
import os

import requests

response = requests.get(
    "https://api.leadity.io/v1/account/analytics",
    headers={
        "Authorization": f"Bearer {os.environ['LEADITY_API_KEY']}",
    },
)

print(response.json())
```

## Response

- `niches`, object[], required.
  - `name`, string, required. The niche's name.
  - `states`, object[], required.
    - `country`, string, required.
    - `state`, string, required.
    - `codesSwept`, integer, required. ZIP or postal codes swept for this niche in this state.
    - `leadsOwned`, integer, required. Delivered leads of this niche the account owns from this state.

## Example response

```json 200
{
  "niches": [
    {
      "name": "Roofing Contractor",
      "states": [
        {
          "country": "US",
          "state": "TX",
          "codesSwept": 412,
          "leadsOwned": 9310
        }
      ]
    }
  ]
}
```

## Errors

Every refusal answers `{ error, message }` with the status below. The full list is on the [Errors](https://docs.leadity.io/errors) page.

| Code | Status | Meaning | Extra fields |
| --- | --- | --- | --- |
| `unauthorized` | 401 | The API key is missing, malformed, revoked or expired. | - |
| `wrong_key_kind` | 401 | This key opens the other surface: an API key works on the HTTP API, an MCP key on the MCP server. | - |
| `account_suspended` | 403 | The account is suspended. | - |
| `email_not_verified` | 403 | The account's email address is not verified yet. | - |
| `rate_limited` | 429 | Too many requests. Wait for the Retry-After seconds and try again. | `retryAfterSeconds`: The seconds to wait, the same number as the Retry-After header. |
| `try_again` | 503 | Leadity could not answer just now. Retry in a moment, with the same Idempotency-Key on a spending call. | `retryAfterSeconds`: When a request with this Idempotency-Key is still being processed: the seconds to wait before retrying with the same key, as the Retry-After header says. |
| `internal_error` | 500 | Something failed on our side. Nothing was charged twice. | `body`: On the MCP server, when Leadity answered in a shape the tool does not publish: that answer as it came. |