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

# Convert a lead list to a Form

> POST /lead/{lead_id}/convert/

Migrates a legacy lead list into a [Form](/api-reference/management-api/forms/create) — Scanova's current, recommended lead-capture builder.

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

<ParamField path="lead_id" type="string" required>
  The lead list's `lead_id`. No request body.
</ParamField>

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

<ResponseExample>
  ```json 201 theme={null}
  {
    "id": 512,
    "form_id": "F3b9c1a2",
    "lead_id": "L9c2f4a1e"
  }
  ```
</ResponseExample>

Converting a lead list:

* Creates a new Form from the lead list's field definitions.
* Re-links every QR Code currently attached to the lead list to the new Form instead.
* Migrates active webhooks to the Form's webhook mechanism (the lead list's own webhooks are marked inactive).
* Migrates any lead notifications configured for this lead list into Form notifications.
* Marks the lead list `is_converted: true` — from this point it no longer appears in [List lead lists](/api-reference/management-api/leads/list) or [List active lead lists](/api-reference/management-api/leads/active-list), and further edits/entries/exports go through the Forms endpoints instead.

<Warning>
  This is not idempotent in a friendly way: calling convert a second time on an already-converted lead list returns `404`, since the lookup filters to non-converted lists. There is no "undo" — check `is_converted` (via [Retrieve a lead list](/api-reference/management-api/leads/retrieve), which will 404 once converted) before retrying.
</Warning>

`400` under `data` if the transformed form data unexpectedly fails Form schema validation (a rare shape-drift edge case, not something a well-formed lead list should trigger).

## Related

* [List lead lists](/api-reference/management-api/leads/list) — lead lists eligible for conversion.
* [Form management](/api-reference/management-api/forms/create) — where the converted resource lives afterward.
* [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/{lead_id}/convert/
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/{lead_id}/convert/:
    post:
      summary: Convert a lead list to a Form
      operationId: convertManagedLeadList
      responses:
        '201':
          description: Converted.
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.

````