> ## 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/{pk}/

获取单条潜在客户提交记录，包括父级潜在客户列表的摘要。

<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 path="pk" type="string" required>
  条目的 UUID，来自[列出潜在客户条目](/zh/api-reference/management-api/leads/entry-list)。
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl --request GET \
    --url 'https://api.scanova.io/lead/L9c2f4a1e/entry/4e6a9b2c-0f77-4d1a-9c6e-3a2b7f9d1e40/' \
    --header 'Authorization: YOUR_API_KEY'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "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",
    "lead_list": {
      "id": 205,
      "lead_id": "L9c2f4a1e",
      "name": "Trade Show Signup",
      "created": "2026-08-16T20:44:51.008000+05:30",
      "is_active": true,
      "usage_count": 2,
      "entries_count": 14,
      "linked_qrs": [],
      "linked_qrs_count": 1,
      "modified": "2026-08-20T09:12:03.441000+05:30"
    }
  }
  ```
</ResponseExample>

如果 `lead_id` 不属于此账户，或 `pk` 不是此潜在客户列表的条目，则返回 `404`。

## 相关内容

* [列出潜在客户条目](/zh/api-reference/management-api/leads/entry-list) —— 查找条目的 `pk`。
* [删除潜在客户条目](/zh/api-reference/management-api/leads/entry-delete) —— 移除此条目。
* [管理 API 概述](/zh/api-reference/management-api/overview) —— 此端点所属的身份验证方案和配额体系。


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /lead/{lead_id}/entry/{pk}/
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/{pk}/:
    get:
      summary: Retrieve a lead entry
      operationId: retrieveManagedLeadEntry
      responses:
        '200':
          description: Lead entry detail.
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.

````