> ## 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 /analytics/report/

列出账户已生成和已保存的分析报告。

<Note>
  需要具有 `MANAGEMENT_API`（或 `MANAGEMENT_API_SANDBOX`）配额的管理 API 密钥 —— 参见[管理 API 概述](/zh/api-reference/management-api/overview) —— 以及账户自身的 `EXPORT_ANALYTICS_REPORT` 配额和 `ANALYTICS_CAN_EXPORT_REPORT` 权限。
</Note>

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

<ResponseExample>
  ```json 200 theme={null}
  {
    "count": 1,
    "next": null,
    "previous": null,
    "results": [
      {
        "id": 58,
        "filter_type": "qrcode",
        "start_date": "2026-08-01",
        "end_date": "2026-08-31",
        "report_type": "both",
        "analytics_format": "xlsx",
        "scan_format": "csv",
        "status": "completed",
        "report_file": "https://cdn.example.com/media/analytics_reports/58/report.xlsx",
        "completed_on": "2026-09-01T08:12:00Z",
        "is_saved": true,
        "saved_name": "Monthly QR Report",
        "created": "2026-09-01T08:10:00Z",
        "requested_by_name": "Docs"
      }
    ]
  }
  ```
</ResponseExample>

随着报告在后台生成，`status` 会从 `new` 变为 `in_progress`，再变为 `completed`（或 `failed`）—— 查询此端点以跟踪通过[生成分析报告](/zh/api-reference/management-api/analytics/report-create)启动的任务。只有当 `status` 为 `completed` 时，`report_file` 和 `completed_on` 才会被填充。

## 相关内容

* [生成分析报告](/zh/api-reference/management-api/analytics/report-create) —— 开始新的报告。
* [获取已保存的分析报告](/zh/api-reference/management-api/analytics/report-retrieve) —— 获取某个报告的详情。
* [管理 API 概述](/zh/api-reference/management-api/overview) —— 此端点所属的身份验证方案和配额体系。


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /analytics/report/
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:
  /analytics/report/:
    get:
      summary: List analytics reports
      description: >-
        Tracking records for the account's generated and saved analytics
        reports.
      operationId: listAnalyticsReports
      responses:
        '200':
          description: Paginated list of reports.
          content:
            application/json:
              example:
                count: 1
                next: null
                previous: null
                results:
                  - id: 58
                    filter_type: qrcode
                    start_date: '2026-08-01'
                    end_date: '2026-08-31'
                    report_type: both
                    analytics_format: xlsx
                    scan_format: csv
                    status: completed
                    report_file: >-
                      https://cdn.example.com/media/analytics_reports/58/report.xlsx
                    completed_on: '2026-09-01T08:12:00Z'
                    is_saved: true
                    saved_name: Monthly QR Report
                    created: '2026-09-01T08:10:00Z'
                    requested_by_name: Docs
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.

````