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

# List device types

> GET /analytics/devices/

Lists device/OS family names usable as the `device` filter value on [QR Code analytics](/api-reference/management-api/analytics/qr-analytics) and related endpoints.

<Note>
  Requires only account authentication — this is a near-static reference list, not account-specific data.
</Note>

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

<ResponseExample>
  ```json 200 theme={null}
  ["iOS", "Android", "Windows", "Mac OS X", "Linux"]
  ```
</ResponseExample>

The response is a flat array of strings, not paginated — use it to populate a device filter/select in your own UI rather than hardcoding the list.

## Related

* [QR Code analytics](/api-reference/management-api/analytics/qr-analytics) — where `device` is used as a filter/breakdown dimension.
* [List countries](/api-reference/management-api/analytics/countries) — the equivalent lookup for countries.
* [List languages](/api-reference/management-api/analytics/languages) — the equivalent lookup for languages.
* [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/devices/
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/devices/:
    get:
      summary: List device types
      description: >-
        Reference list of device/OS family names usable as the `device` filter
        value on QR analytics endpoints.
      operationId: listAnalyticsDeviceTypes
      responses:
        '200':
          description: List of device types.
          content:
            application/json:
              example:
                - iOS
                - Android
                - Windows
                - Mac OS X
                - Linux
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.

````