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

# Get lead analytics

> POST /lead/analytics/

Returns aggregated analytics (entry counts, conversion breakdown, and traffic source) for one or more lead lists.

<Note>
  Requires a Management API key with `MANAGEMENT_API` (or `MANAGEMENT_API_SANDBOX`) quota, and the `LEAD_GENERATION_ANALYTICS_CAN_VIEW` permission, sent as the raw `Authorization` header value — see the [Management API overview](/api-reference/management-api/overview).
</Note>

<ParamField body="q" type="array" required>
  An array of strings identifying the lead lists to analyze — either `lead_id`s or QR `url_hash`es, depending on `filter_by`.
</ParamField>

<ParamField body="filter_by" type="string" default="lead_id">
  `lead_id` (default) or `qr_hash`.
</ParamField>

<ParamField query="type" type="string" default="entries_count">
  Comma-separated subset of `entries_count`, `leads_conversion`, `source` to compute.
</ParamField>

<ParamField query="from" type="string">
  Start date (`YYYY-MM-DD`). Defaults to 7 days before `to`.
</ParamField>

<ParamField query="to" type="string">
  End date (`YYYY-MM-DD`). Defaults to today.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl --request POST \
    --url 'https://api.scanova.io/lead/analytics/?type=entries_count,leads_conversion,source&from=2026-08-01&to=2026-08-31' \
    --header 'Authorization: YOUR_API_KEY' \
    --header 'Content-Type: application/json' \
    --data '{ "q": ["L9c2f4a1e"], "filter_by": "lead_id" }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "entries_count": {
      "total": 14,
      "elevation": { "percent": 12, "previous": 12, "type": "+", "period": { "start": "2026-07-01", "end": "2026-08-01" } }
    },
    "leads_conversion": {
      "all": [["2026-08-01", 3], ["2026-08-02", 1]],
      "leads": [["2026-08-01", 2], ["2026-08-02", 1]],
      "skip": [["2026-08-01", 1], ["2026-08-02", 0]]
    },
    "source": [["Booth QR", 9.0], ["Flyer QR", 5.0]]
  }
  ```
</ResponseExample>

`elevation` is `null` when both the requested period and its prior comparison period have zero entries, to avoid a misleading percentage. `400` under `q` if it's missing or empty — this endpoint's contract is `{"q": [...], "filter_by": "..."}`, not `{"lead_list": [...], "date_from": "...", "date_to": "..."}` from an older, incompatible shape.

## Related

* [Export lead analytics](/api-reference/management-api/leads/analytics-export) — download these same breakdowns as a file.
* [List lead lists](/api-reference/management-api/leads/list) — find `lead_id` values to analyze.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota architecture this endpoint is part of.


## OpenAPI

````yaml api-reference/openapi/management-api.json POST /lead/analytics/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    api.scanova.io (QR codes, folders, tags, leads, forms, analytics, plans,
    shared users & roles), plus the token-creation and usage-stats endpoints
    used to authenticate against it. Every path and request/response shape below
    was verified live against a real API key and the actual running backend
    (Phase 7, 2026-08-16) — not guessed from reading urls.py alone.
  version: 2.0.0
servers:
  - url: https://api.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /lead/analytics/:
    post:
      summary: Get lead analytics
      operationId: getManagedLeadAnalytics
      responses:
        '200':
          description: Aggregated analytics for the requested lead lists.
components:
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        Send your Management API key as the raw value of the Authorization
        header — no "Bearer " or "Token " prefix, and no other characters.
        Example: `Authorization: 401f7ac837da42b97f613d789819ff93537bee6a`. A
        header containing more than one space-separated part is rejected
        outright. Requests also require the request's Host header to be the
        management API host (e.g. api.scanova.io) — the same key sent to the
        regular API host will not authenticate.

````