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

# 列出潜在客户条目

> GET /lead/{lead_id}/entry/

列出潜在客户列表表单收集到的提交（"条目"）。

<Note>
  需要具有 `MANAGEMENT_API`（或 `MANAGEMENT_API_SANDBOX`）配额和 `LEAD_GENERATION_ENTRY_CAN_VIEW` 权限的管理 API 密钥，作为原始 `Authorization` 标头值发送 —— 参见[管理 API 概述](/zh/api-reference/management-api/overview)。
</Note>

<ParamField path="lead_id" type="string" required>
  潜在客户列表的 `lead_id`。
</ParamField>

<ParamField query="qr_id" type="string">
  按 `qrid` 筛选通过特定 QR 码提交的条目。
</ParamField>

<ParamField query="created_from" type="string">
  仅包含在此日期（含）之后创建的条目（`YYYY-MM-DD`）。
</ParamField>

<ParamField query="created_till" type="string">
  仅包含在此日期（含）之前创建的条目（`YYYY-MM-DD`）。
</ParamField>

<ParamField query="search" type="string">
  在所有已提交的字段值中进行子字符串搜索 —— 由于潜在客户表单字段是按列表由管理员定义的，因此没有固定的可搜索列，此参数会匹配条目原始数据中的任何位置。
</ParamField>

<ParamField query="ordering" type="string">
  `created` 或 `-created`。默认值为 `-created`。
</ParamField>

<ParamField query="page" type="integer">
  页码。
</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` 是条目的 UUID（在下方的获取/删除端点中用作 `pk`），`lead_list_id`/`qr_code_id` 通过字符串标识符（`lead_id`/`qrid`）而非数字 id 引用父级潜在客户列表和提交所用的 QR 码。如果 `lead_id` 不属于此账户，则返回 `404`。

## 相关内容

* [获取潜在客户条目](/zh/api-reference/management-api/leads/entry-retrieve) —— 获取某条目的完整详情。
* [导出潜在客户条目](/zh/api-reference/management-api/leads/entry-export) —— 将条目下载为 CSV/XLSX。
* [管理 API 概述](/zh/api-reference/management-api/overview) —— 此端点所属的身份验证方案和配额体系。


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

````