curl -X POST "https://api.scanova.io/qr/trash/delete/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"ids": [
"Qe5f6g7h8i9j0k1l"
]
}'
QR Codes
Permanently delete trashed QR Codes
POST /qr/trash/delete/
POST
/
qr
/
trash
/
delete
/
curl -X POST "https://api.scanova.io/qr/trash/delete/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"ids": [
"Qe5f6g7h8i9j0k1l"
]
}'
Permanently removes QR Codes that are already in Trash.
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
POST https://api.scanova.io/qr/trash/delete/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
array
required
qrid values to delete permanently, or the single-element sentinel ["all"].curl -X POST "https://api.scanova.io/qr/trash/delete/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"ids": [
"Qe5f6g7h8i9j0k1l"
]
}'
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.
400. Related suspicious-QR records are hard-deleted alongside the QR Code, in the same transaction.
Related
- List trashed QR Codes — find the ids to delete.
- Restore trashed QR Codes — the reversible alternative.
- Check GS1 references — find out whether this delete will be blocked.
- Delete a QR Code — the soft delete that must happen first.
- QR Manager overview — the quotas, role permissions, and Trash model shared by every endpoint in this module.
- Management API overview — the auth scheme and quota rules that apply to this endpoint.
Authorizations
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.
Response
QR codes permanently deleted.
Was this page helpful?