curl -X POST "https://api.scanova.io/qr/multi-delete/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"ids": [
"Qa1b2c3d4e5f6g7h8",
"Qb2c3d4e5f6g7h8i9"
]
}'
{
"ids": [
"QR Codes does not exists"
]
}QR Codes
Delete many QR Codes
POST /qr/multi-delete/
POST
/
qr
/
multi-delete
/
curl -X POST "https://api.scanova.io/qr/multi-delete/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"ids": [
"Qa1b2c3d4e5f6g7h8",
"Qb2c3d4e5f6g7h8i9"
]
}'
{
"ids": [
"QR Codes does not exists"
]
}Soft-deletes many QR Codes in one call. They move to Trash, exactly as with a single Delete a QR Code.
POST https://api.scanova.io/qr/multi-delete/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
array
required
qrid values to delete, or the single-element sentinel ["all"] to select everything the filter allows.object
A JSON object reusing the List QR Codes filter set, to select QR Codes by criteria rather than by id.
object
A JSON search specification, applied alongside
filter.curl -X POST "https://api.scanova.io/qr/multi-delete/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"ids": [
"Qa1b2c3d4e5f6g7h8",
"Qb2c3d4e5f6g7h8i9"
]
}'
filter distinguishes an explicitly-null folder from an absent one:"filter": {"folder": null}means uncategorized QR Codes only.- A
filterwith nofolderkey at all means no folder restriction.
The same GS1 referential-integrity guard as the single delete runs here: if any selected QR Code is a GS1 resolution target or a GS1 parent with child variants, the call is refused with
400 rather than deleting the rest.Related
- Delete a QR Code — the single-QR equivalent.
- List QR Codes — the filter set
filterreuses. - Restore trashed QR Codes — undo a bulk delete.
- Permanently delete trashed QR Codes — make it irreversible.
- 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 moved to Trash.
Was this page helpful?