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

> GET /lead/{lead_id}/entry/

Lists submissions ("entries") collected by a lead list's form.

<Note>
  Requires a Management API key with `MANAGEMENT_API` (or `MANAGEMENT_API_SANDBOX`) quota, and the `LEAD_GENERATION_ENTRY_CAN_VIEW` permission, 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`.
</ParamField>

<ParamField query="qr_id" type="string">
  Filters to entries submitted through a specific QR Code, by `qrid`.
</ParamField>

<ParamField query="created_from" type="string">
  Only entries created on or after this date (`YYYY-MM-DD`).
</ParamField>

<ParamField query="created_till" type="string">
  Only entries created on or before this date (`YYYY-MM-DD`).
</ParamField>

<ParamField query="search" type="string">
  Substring search across all submitted field values — since lead-form fields are admin-defined per list, there's no fixed column to search, so this matches anywhere in the entry's raw data.
</ParamField>

<ParamField query="ordering" type="string">
  `created` or `-created`. Default is `-created`.
</ParamField>

<ParamField query="page" type="integer">
  Page number.
</ParamField>

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

<ResponseExample>
  ```json 200 theme={null}
  {
    "count": 14,
    "next": "https://api.scanova.io/lead/L9c2f4a1e/entry/?page=2",
    "previous": null,
    "results": [
      {
        "id": "4e6a9b2c-0f77-4d1a-9c6e-3a2b7f9d1e40",
        "lead_list_id": "L9c2f4a1e",
        "qr_code_id": "Q7f3a",
        "data": [{ "question": "Email", "answer": "alice@example.com" }],
        "tracking_data_id": "8b1d4e2a-1c3f-4a9d-9e21-5f6a7b8c9d10",
        "created": "2026-09-01T10:03:12.552000+05:30"
      }
    ]
  }
  ```
</ResponseExample>

`id` is the entry's UUID (used as `pk` on the retrieve/delete endpoints below), and `lead_list_id`/`qr_code_id` reference the parent lead list and submitting QR Code by their string identifiers (`lead_id`/`qrid`), not numeric ids. `404` if `lead_id` isn't owned by this account.

## Related

* [Retrieve a lead entry](/api-reference/management-api/leads/entry-retrieve) — get one entry's full detail.
* [Export lead entries](/api-reference/management-api/leads/entry-export) — download entries as CSV/XLSX.
* [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/{lead_id}/entry/
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}/entry/:
    get:
      summary: List lead entries
      operationId: listManagedLeadEntries
      responses:
        '200':
          description: Paginated list of lead submissions.
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.

````