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

# Delete a child QR Code

> DELETE /qr/{parent_qrid}/children/{child_qrid}/

Permanently deletes one child variant.

```
DELETE https://api.scanova.io/qr/{parent_qrid}/children/{child_qrid}/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField path="parent_qrid" type="string" required>
  The `qrid` of the GS1 parent QR Code.
</ParamField>

<ParamField path="child_qrid" type="string" required>
  The `qrid` of the child variant to delete.
</ParamField>

<ParamField body="keep_tracking" type="boolean" default="false">
  Optional. Retain the child's scan-tracking rows after the variant itself is gone.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X DELETE "https://api.scanova.io/qr/Qz9y8x7w6v5u4t3s/children/Qc3d4e5f6g7h8i9j0/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -H "Content-Type: application/json" \
    -d '{
        "keep_tracking": false
    }'
  ```
</RequestExample>

<Warning>
  This delete is **immediate and permanent**. Unlike [Delete a QR Code](/api-reference/management-api/qr/delete), it does **not** go through Trash and cannot be restored — a child variant has no standalone detail page to restore to. Confirm with the user before calling.
</Warning>

Returns `204 No Content`. Pass `keep_tracking: true` to keep the historical scan data for reporting after the variant is removed.

## Related

* [List and create child QR Codes](/api-reference/management-api/qr/child-list-create) — the collection this removes from.
* [Delete a QR Code](/api-reference/management-api/qr/delete) — the soft-delete flow that applies to ordinary QR Codes.
* [QR Manager overview](/api-reference/management-api/qr/overview) — the quotas, role permissions, and Trash model shared by every endpoint in this module.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota rules that apply to this endpoint.


## OpenAPI

````yaml api-reference/openapi/management-api.json DELETE /qr/{parent_qrid}/children/{child_qrid}/
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:
  /qr/{parent_qrid}/children/{child_qrid}/:
    delete:
      summary: Permanently delete a child QR code
      description: >-
        IMMEDIATE, PERMANENT delete — this is NOT the soft-delete/Trash flow
        used elsewhere in this module, because a child has no standalone detail
        page to restore to. The optional body flag `keep_tracking` (default
        false) retains the child's scan-tracking rows.
      operationId: deleteChildQrCode
      parameters:
        - name: parent_qrid
          in: path
          required: true
          schema:
            type: string
          description: The `qrid` of the GS1 parent QR code.
        - name: child_qrid
          in: path
          required: true
          schema:
            type: string
          description: The `qrid` of the child variant to delete.
      requestBody:
        content:
          application/json:
            example:
              keep_tracking: false
      responses:
        '204':
          description: Child permanently deleted.
        '404':
          description: No such child under this parent for 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.

````