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

# List lead lists

> GET /lead/

Lead lists are Scanova's original lead-capture feature — a form definition (`data`) attached to a QR code's landing page. List or create them here.

<Warning>
  Lead Lists are a **legacy** feature. Scanova's dashboard now steers new lead-capture use cases toward [Forms](/api-reference/management-api/forms/create) instead, which cover the same "collect visitor data from a QR scan" use case with a more capable builder. Existing lead lists keep working, and this endpoint is unaffected, but build new integrations against Forms unless you specifically need to manage a pre-existing lead list.
</Warning>

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

<RequestExample>
  ```bash cURL theme={null}
  curl --request GET \
    --url 'https://management.scanova.io/lead/' \
    --header 'Authorization: YOUR_API_KEY'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "count": 0,
    "next": null,
    "previous": null,
    "results": []
  }
  ```
</ResponseExample>

<Note>
  Verified live against a test account with no lead lists — hence the empty `results`. This endpoint only ever returns lead lists that have **not** been converted to a Form; once a lead list is converted (via the dashboard's "Migrate to Form" flow), it drops out of this list permanently and becomes reachable only through the Forms endpoints.
</Note>

<ParamField query="is_active" type="boolean">
  Filter to active (`true`) or inactive (`false`) lead lists. Inactive lead lists don't render their form on the landing page.
</ParamField>

### Response fields (per entry)

<ResponseField name="id" type="integer" />

<ResponseField name="lead_id" type="string">
  Unique, immutable lead-list identifier.
</ResponseField>

<ResponseField name="name" type="string">
  Internal name — not shown on the public landing page.
</ResponseField>

<ResponseField name="is_active" type="boolean" />

<ResponseField name="usage_count" type="integer">
  Number of QR codes this lead list is currently attached to.
</ResponseField>

<ResponseField name="entries_count" type="integer">
  Total number of lead submissions collected.
</ResponseField>

<ResponseField name="linked_qrs" type="array">
  QR codes this lead list is attached to.
</ResponseField>

<ResponseField name="created" type="string" />

<ResponseField name="modified" type="string" />

## Related

* [Create a lead list](/api-reference/management-api/leads/create) — the other operation on this same endpoint.
* [Form management](/api-reference/management-api/forms/create) — the current, recommended lead-capture builder this legacy feature is being steered toward.
* [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 GET /lead/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    management.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://management.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /lead/:
    get:
      summary: List lead lists
      operationId: listManagedLeadLists
      responses:
        '200':
          description: List of 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. management.scanova.io) — the same key sent to
        the regular API host will not authenticate.

````