> ## 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 API keys

> GET /web-tracking/sites/{site_id}/api-keys/

Lists the server-side API keys issued for a tracking site — used to authenticate `POST /server-events` calls against the [Conversion Tracking API](/conversion-tracking/server/send-events), not the Management API itself.

<Note>
  Requires the account's `CONVERSION_TRACKING` quota. The raw key value is only ever returned once, at [generation time](/api-reference/management-api/web-tracking/api-key-generate) — this list only exposes the `prefix`.
</Note>

<ParamField path="site_id" type="integer" required>
  Tracking site ID.
</ParamField>

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

<ResponseExample>
  ```json 200 theme={null}
  [
    {
      "id": 5,
      "name": "Server key",
      "prefix": "aZ3kP9x1",
      "is_active": true,
      "created": "2026-09-01T10:06:00+05:30",
      "modified": "2026-09-01T10:06:00+05:30"
    }
  ]
  ```
</ResponseExample>

## Related

* [Generate an API key](/api-reference/management-api/web-tracking/api-key-generate)
* [Retrieve / update / delete an API key](/api-reference/management-api/web-tracking/api-key-retrieve)
* [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 /web-tracking/sites/{site_id}/api-keys/
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:
  /web-tracking/sites/{site_id}/api-keys/:
    get:
      summary: List API keys
      operationId: listTrackingSiteApiKeys
      parameters:
        - name: site_id
          in: path
          required: true
          schema:
            type: integer
      responses:
        '200':
          description: API keys for this site (never includes the raw key).
          content:
            application/json:
              example:
                - id: 5
                  name: Server key
                  prefix: aZ3kP9x1
                  is_active: true
                  created: '2026-09-01T10:06:00+05:30'
                  modified: '2026-09-01T10:06:00+05:30'
        '404':
          description: No site with this id owned by 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.

````