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

# Permanently delete trashed QR Codes

> POST /qr/trash/delete/

Permanently removes QR Codes that are already in Trash.

```
POST   https://api.scanova.io/qr/trash/delete/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField body="ids" type="array" required>
  `qrid` values to delete permanently, or the single-element sentinel `["all"]`.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://api.scanova.io/qr/trash/delete/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -H "Content-Type: application/json" \
    -d '{
        "ids": [
            "Qe5f6g7h8i9j0k1l"
        ]
    }'
  ```
</RequestExample>

<Warning>
  **This is irreversible.** It is a hard delete: the rows leave the database and no restore is possible. It only ever operates on QR Codes that are **already soft-deleted** — it is not a shortcut past Trash for a live QR Code.
</Warning>

The GS1 referential-integrity guard applies here too: a QR Code that is a GS1 resolution target, or a GS1 parent with child variants, is refused with `400`. Related suspicious-QR records are hard-deleted alongside the QR Code, in the same transaction.

## Related

* [List trashed QR Codes](/api-reference/management-api/qr/trash-list) — find the ids to delete.
* [Restore trashed QR Codes](/api-reference/management-api/qr/trash-restore) — the reversible alternative.
* [Check GS1 references](/api-reference/management-api/qr/gs1-references) — find out whether this delete will be blocked.
* [Delete a QR Code](/api-reference/management-api/qr/delete) — the soft delete that must happen first.
* [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 POST /qr/trash/delete/
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/trash/delete/:
    post:
      summary: Permanently delete trashed QR codes
      description: >-
        Hard delete, irreversible. Only operates on rows that are already
        soft-deleted. The same GS1 referential-integrity guards as the other
        delete paths apply, and related SuspiciousQRCode rows are hard-deleted
        in the same transaction.
      operationId: permanentlyDeleteTrashedQrCodes
      requestBody:
        content:
          application/json:
            example:
              ids:
                - Qe5f6g7h8i9j0k1l
      responses:
        '204':
          description: QR codes permanently deleted.
        '400':
          description: >-
            Nothing matched, a selected QR code is not in Trash, or the GS1
            referential-integrity guard blocked the delete.
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.

````