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

# Aktivitäts-Meilenstein-Kennzeichen abrufen

> GET /user-logs/user-activity/

Ruft die aktuellen Feature-Nutzungs-Meilenstein-Kennzeichen des Kontos ab, auf dem **Management-API**-Host (`api.scanova.io`), authentifiziert mit Ihrem rohen Management-API-Schlüssel.

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

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

<ResponseExample>
  ```json 200 theme={null}
  {
    "qr_static_created": true,
    "qr_dynamic_created": true,
    "feature_password_protection": false,
    "lead_list_created": false,
    "onboarding_1_continue_clicked": true,
    "qr_first_created": "2026-06-01T10:00:00Z",
    "total_qr_codes": 24,
    "total_shared_users": 3
  }
  ```
</ResponseExample>

Rund 50 boolesche Felder verfolgen, ob das Konto jemals eine bestimmte Aktion durchgeführt hat (z. B. `qr_static_created`, `feature_password_protection`, `lead_list_created`) — einmal `true`, kehrt ein Kennzeichen nie zu `false` zurück. Einige wenige Felder sind berechnet statt boolesch, wie `qr_first_created` und `total_qr_codes`.

## Verwandte Themen

* [Aktivitäts-Meilenstein-Kennzeichen setzen](/de/api-reference/management-api/user-logs/user-activity-update) — ein Kennzeichen auf `true` setzen.
* [Übersicht über die Management API](/de/api-reference/management-api/overview) — das Authentifizierungsschema und die Quota-Regeln für diesen Endpunkt.


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /user-logs/user-activity/
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/user-activity/:
    get:
      summary: Retrieve activity milestone flags
      description: >-
        The account's current state across ~50 boolean feature-usage milestones
        (e.g. `qr_static_created`, `feature_password_protection`), plus a few
        computed totals.
      operationId: retrieveUserActivity
      responses:
        '200':
          description: The account's activity flags.
          content:
            application/json:
              example:
                qr_static_created: true
                qr_dynamic_created: true
                feature_password_protection: false
                lead_list_created: false
                onboarding_1_continue_clicked: true
                qr_first_created: '2026-06-01T10:00:00Z'
                total_qr_codes: 24
                total_shared_users: 3
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.

````