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

# Listar listas de leads activas

> GET /lead/active/

Devuelve una lista de forma mínima de las listas de leads que están tanto activas como aún no convertidas a un Formulario — útil para poblar un selector de "elegir una lista de leads" sin los campos de detalle más pesados.

<Note>
  Requiere una clave de API de gestión con cuota `MANAGEMENT_API` (o `MANAGEMENT_API_SANDBOX`), enviada como el valor sin procesar del encabezado `Authorization` — consulte el [resumen de la API de gestión](/es/api-reference/management-api/overview).
</Note>

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

<ResponseExample>
  ```json 200 theme={null}
  [
    { "id": 205, "lead_id": "L9c2f4a1e", "name": "Trade Show Signup", "created": "2026-08-16T20:44:51.008000+05:30" }
  ]
  ```
</ResponseExample>

La respuesta es un array plano, no paginado, y solo incluye `id`, `lead_id`, `name` y `created` — para la forma de detalle completa, use [Obtener una lista de leads](/es/api-reference/management-api/leads/retrieve).

## Relacionado

* [Listar listas de leads](/es/api-reference/management-api/leads/list) — la lista paginada completa, incluidas las listas inactivas.
* [Obtener una lista de leads](/es/api-reference/management-api/leads/retrieve) — la forma de detalle completa de una entrada aquí.
* [Resumen de la API de gestión](/es/api-reference/management-api/overview) — el esquema de autenticación y la arquitectura de cuotas a la que pertenece este endpoint.


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /lead/active/
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/active/:
    get:
      summary: List active lead lists
      operationId: listActiveManagedLeadLists
      responses:
        '200':
          description: Minimal-shape list of active, non-converted 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.

````