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

# Retrieve / update / delete a tracking site

> GET, PATCH, DELETE /web-tracking/sites/{pk}/

Fetches, renames/toggles, or removes a single tracking site, including its nested domains, API keys, and QR attachments.

<Note>
  Requires the account's `CONVERSION_TRACKING` quota. Only sites owned by the requesting account are visible — another account's site returns `404`.
</Note>

<ParamField path="pk" type="integer" required>
  Tracking site ID, from [List tracking sites](/api-reference/management-api/web-tracking/sites-list-create).
</ParamField>

<ParamField body="name" type="string">
  New display name (PATCH only).
</ParamField>

<ParamField body="is_active" type="boolean">
  Toggle the site on/off (PATCH only) — an inactive site's SDK/server events are typically still accepted at the ingestion layer but excluded from reporting; treat this as a display-level pause, not a hard kill switch.
</ParamField>

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

  ```bash cURL Update theme={null}
  curl --request PATCH \
    --url 'https://api.scanova.io/web-tracking/sites/7/' \
    --header 'Authorization: YOUR_API_KEY' \
    --header 'Content-Type: application/json' \
    --data '{"name": "Marketing site (EU)"}'
  ```

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

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": 7,
    "site_id": "aZ3kP9...64-char-random-id",
    "name": "Marketing site (EU)",
    "is_active": true,
    "verified_on": "2026-09-05T09:00:00+05:30",
    "is_verified": true,
    "created": "2026-09-01T10:00:00+05:30",
    "modified": "2026-09-09T08:10:00+05:30",
    "domains": [
      {"id": 3, "domain": "example.com", "created": "2026-09-01T10:05:00+05:30", "modified": "2026-09-01T10:05:00+05:30"}
    ],
    "api_keys": [
      {"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"}
    ],
    "qrs": [
      {"id": 2, "site": {"id": 7, "site_id": "aZ3kP9...", "name": "Marketing site (EU)", "is_active": true, "verified_on": "2026-09-05T09:00:00+05:30", "is_verified": true, "created": "2026-09-01T10:00:00+05:30", "modified": "2026-09-09T08:10:00+05:30"}, "dynamic_url_object": 501, "is_active": true, "created": "2026-09-02T11:00:00+05:30", "modified": "2026-09-02T11:00:00+05:30"}
    ]
  }
  ```
</ResponseExample>

`204` on delete — cascades to the site's domains, API keys, QR attachments, and funnels.

## Related

* [List / create tracking sites](/api-reference/management-api/web-tracking/sites-list-create)
* [List / add domains](/api-reference/management-api/web-tracking/domains-list-create)
* [List / attach QR Codes](/api-reference/management-api/web-tracking/qrs-list-create)
* [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/{pk}/
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/{pk}/:
    get:
      summary: Retrieve a tracking site
      operationId: getTrackingSite
      parameters:
        - name: pk
          in: path
          required: true
          schema:
            type: integer
      responses:
        '200':
          description: One tracking site with nested domains/api_keys/qrs.
          content:
            application/json:
              example:
                id: 7
                site_id: aZ3kP9...64-char-random-id
                name: Marketing site
                is_active: true
                verified_on: '2026-09-05T09:00:00+05:30'
                is_verified: true
                created: '2026-09-01T10:00:00+05:30'
                modified: '2026-09-09T08:10:00+05:30'
                domains:
                  - id: 3
                    domain: example.com
                    created: '2026-09-09T08:00:00+05:30'
                    modified: '2026-09-09T08:00:00+05:30'
                api_keys:
                  - 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'
                qrs:
                  - id: 2
                    site:
                      id: 7
                      site_id: aZ3kP9...64-char-random-id
                      name: Marketing site
                      is_active: true
                      verified_on: '2026-09-05T09:00:00+05:30'
                      is_verified: true
                      created: '2026-09-01T10:00:00+05:30'
                      modified: '2026-09-09T08:10:00+05:30'
                    dynamic_url_object: 501
                    is_active: true
                    created: '2026-09-09T08:15:00+05:30'
                    modified: '2026-09-09T08:15: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.

````