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

# Analytics overview

> GET /analytics/overview/

Returns an account-wide scan analytics dashboard aggregate — across every QR Code on the account, not scoped to any single resource.

<Note>
  Requires a Management API key with `MANAGEMENT_API` (or `MANAGEMENT_API_SANDBOX`) quota — see the [Management API overview](/api-reference/management-api/overview) — plus the account's own `QR_ANALYTICS_OVERVIEW` quota and `ANALYTICS_CAN_VIEW` permission.
</Note>

<ParamField query="type" type="string">
  Comma-separated subset of `all_time`, `current_month`, `last_months`, `scan_dates` to include. Omit for all of them.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl --request GET \
    --url 'https://api.scanova.io/analytics/overview/?type=all_time,current_month,last_months,scan_dates' \
    --header 'Authorization: YOUR_API_KEY'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "all_time": { "total_scans": 18420, "total_qr_codes": 96 },
    "current_month": { "total_scans": 1204, "unique_scans": 980 },
    "last_months": [["2026-06", 3120], ["2026-07", 4410], ["2026-08", 3980]],
    "scan_dates": [["2026-09-01", 42], ["2026-09-02", 51]]
  }
  ```
</ResponseExample>

This is the same aggregate backing the dashboard's overview widget — it has no request body and no way to scope to a specific QR Code, tag, or folder. For scoped analytics on a set of QR Codes, use [QR Code analytics](/api-reference/management-api/analytics/qr-analytics) instead.

## Related

* [QR Code analytics](/api-reference/management-api/analytics/qr-analytics) — scoped analytics for specific QR Codes, tags, or folders.
* [List analytics reports](/api-reference/management-api/analytics/report-list) — generate a downloadable report instead of a live aggregate.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota architecture this endpoint is part of.


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /analytics/overview/
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/overview/:
    get:
      summary: Get the account analytics overview
      description: >-
        Account-wide scan analytics dashboard aggregate, across every QR code on
        the account.
      operationId: getAnalyticsOverview
      parameters:
        - name: type
          in: query
          schema:
            type: string
          description: >-
            Comma-separated subset of `all_time`, `current_month`,
            `last_months`, `scan_dates`.
      responses:
        '200':
          description: Account-wide analytics overview.
          content:
            application/json:
              example:
                all_time:
                  total_scans: 18420
                  total_qr_codes: 96
                current_month:
                  total_scans: 1204
                  unique_scans: 980
                last_months:
                  - - 2026-06
                    - 3120
                  - - 2026-07
                    - 4410
                  - - 2026-08
                    - 3980
                scan_dates:
                  - - '2026-09-01'
                    - 42
                  - - '2026-09-02'
                    - 51
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.

````