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

# Create a lead list

> POST /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 POST \
    --url 'https://management.scanova.io/lead/' \
    --header 'Authorization: YOUR_API_KEY' \
    --header 'Content-Type: application/json' \
    --data '{
      "name": "Trade Show Signup",
      "data": "{\"fields\":[{\"type\":\"email\",\"label\":\"Email\",\"required\":true}]}"
    }'
  ```
</RequestExample>

<ResponseExample>
  ```json 201 theme={null}
  {
    "id": 205,
    "lead_id": "L9c2f4a1e",
    "name": "Trade Show Signup",
    "created": "2026-08-16T20:44:51.008000+05:30",
    "is_active": true,
    "usage_count": 0,
    "entries_count": 0,
    "linked_qrs": [],
    "modified": "2026-08-16T20:44:51.008000+05:30",
    "data": "{\"fields\":[{\"type\":\"email\",\"label\":\"Email\",\"required\":true}]}",
    "webhooks": []
  }
  ```
</ResponseExample>

<ParamField body="name" type="string" required>
  Lead list name, up to 128 characters.
</ParamField>

<ParamField body="data" type="string" required>
  A JSON-encoded string (not a raw object) describing the lead form's fields. Validated against the same lead-form schema the dashboard's lead-list builder uses — malformed JSON or a schema violation returns a 400 under `data`.
</ParamField>

<ParamField body="is_active" type="boolean" default="true">
  Whether the form renders on the landing page.
</ParamField>

<Note>
  The response includes `data` and `webhooks` (a list of `{id, url, created, modified}` notification webhooks) — fields only present on the detail shape returned by create/retrieve, not on the list endpoint above.
</Note>

## Related

* [List lead lists](/api-reference/management-api/leads/list) — 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 POST /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/:
    post:
      summary: Create a lead list
      operationId: createManagedLeadList
      responses:
        '201':
          description: Lead list created
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.

````