> ## 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 /campaign/active/user-log/

在 **Management API** 主机（`api.scanova.io`）上返回已认证账户针对当前有效 G2 评价活动的日志记录，使用您的原始 Management API 密钥进行身份验证。

```
GET https://api.scanova.io/campaign/active/user-log/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

将此端点与[获取当前有效的评价活动](/zh/api-reference/management-api/campaign/active)配合使用，以决定是否展示提示：如果存在有效活动，且此调用返回 `404` 或 `is_popup_disabled` 为 `false`，则展示;否则不展示。

<RequestExample>
  ```bash cURL theme={null}
  curl "https://api.scanova.io/campaign/active/user-log/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": 118,
    "is_popup_disabled": false
  }
  ```
</ResponseExample>

## 为何此端点经常返回 404

此端点在两种不同情况下都会返回 `404`，但对调用方而言二者含义相同——"展示弹窗"：

* 当前根本没有正在进行的活动（与 [`GET /campaign/active/`](/zh/api-reference/management-api/campaign/active) 返回 `404` 的条件相同）。
* *确实*存在有效活动，但该账户尚未记录与其的任何互动——日志记录是延迟创建的，仅在首次调用 [`POST /campaign/user-log/`](/zh/api-reference/management-api/campaign/user-log-create) 时创建，而不是在活动开始时自动创建。

## 相关内容

* [获取当前有效的评价活动](/zh/api-reference/management-api/campaign/active)——此日志记录所对应的活动。
* [记录弹窗已展示、已关闭或已提交](/zh/api-reference/management-api/campaign/user-log-create)——创建此端点所读取的记录。
* [更新您的活动日志](/zh/api-reference/management-api/campaign/user-log-update)——更新此端点所读取的记录。
* [Management API 概览](/zh/api-reference/management-api/overview)——适用于此端点的身份验证方案和配额规则。


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /campaign/active/user-log/
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:
  /campaign/active/user-log/:
    get:
      summary: Get your dismissal state for the active campaign
      description: >-
        Returns whether the authenticated account has already interacted with
        the popup for the currently active campaign. Returns 404 if there's no
        active campaign, or if this account has no log row for it yet — both
        cases mean "show the popup".
      operationId: getManagedActiveCampaignUserLog
      responses:
        '200':
          description: The account's log row for the active campaign.
          content:
            application/json:
              example:
                id: 118
                is_popup_disabled: false
        '404':
          description: No active campaign, or no log row yet for this account.
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.

````