> ## 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 /user-logs/activity-summary/

在**管理 API** 主机 (`api.scanova.io`) 上返回按事件类别汇总的每日活动计数，使用您的原始管理 API 密钥进行身份验证。

```
GET https://api.scanova.io/user-logs/activity-summary/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField query="from" type="string">
  起始日期（`YYYY-MM-DD`）。默认为 `to` 之前 30 天。
</ParamField>

<ParamField query="to" type="string">
  结束日期（`YYYY-MM-DD`）。默认为今天。
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl "https://api.scanova.io/user-logs/activity-summary/?from=2026-08-01&to=2026-08-31" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  [
    { "date": "2026-08-20", "event_category": "qr_created", "count": 4, "first_at": "2026-08-20T09:01:00Z", "last_at": "2026-08-20T17:44:00Z" },
    { "date": "2026-08-20", "event_category": "login", "count": 1, "first_at": "2026-08-20T08:55:00Z", "last_at": "2026-08-20T08:55:00Z" }
  ]
  ```
</ResponseExample>

响应是一个扁平数组 —— 每个含有至少一个事件的 `date` × `event_category` 组合对应一行，而非分页对象。与[列出精选活动动态事件](/zh/api-reference/management-api/user-logs/activity-feed)不同，此端点仅限账户所有者层级，不会针对标签受限的共享用户进行范围缩减。

## 相关内容

* [列出精选活动动态事件](/zh/api-reference/management-api/user-logs/activity-feed) —— 这些汇总背后的具体事件。
* [获取最新的 AI 活动洞察](/zh/api-reference/management-api/user-logs/activity-insight) —— 基于同一数据构建的叙述性摘要。
* [管理 API 概述](/zh/api-reference/management-api/overview) —— 适用于此端点的身份验证方案和配额规则。


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /user-logs/activity-summary/
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:
  /user-logs/activity-summary/:
    get:
      summary: Get daily activity stats
      description: >-
        Daily rollup counts per event category, for charting. Defaults to the
        trailing 30 days. Owner-level only — not tag-scoped for shared users.
      operationId: getActivitySummary
      parameters:
        - name: from
          in: query
          schema:
            type: string
            format: date
        - name: to
          in: query
          schema:
            type: string
            format: date
      responses:
        '200':
          description: Array of daily rollups.
          content:
            application/json:
              example:
                - date: '2026-08-20'
                  event_category: qr_created
                  count: 4
                  first_at: '2026-08-20T09:01:00Z'
                  last_at: '2026-08-20T17:44:00Z'
                - date: '2026-08-20'
                  event_category: login
                  count: 1
                  first_at: '2026-08-20T08:55:00Z'
                  last_at: '2026-08-20T08:55:00Z'
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.

````