curl -X PATCH "https://api.scanova.io/qr/Qa1b2c3d4e5f6g7h8/change-category/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"category": 8
}'
{
"qr_type": ["Edit category on static QR codes is not allowed."]
}
QR Codes
Change a QR Code's category
PATCH /qr//change-category/
PATCH
/
qr
/
{qrid}
/
change-category
/
curl -X PATCH "https://api.scanova.io/qr/Qa1b2c3d4e5f6g7h8/change-category/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"category": 8
}'
{
"qr_type": ["Edit category on static QR codes is not allowed."]
}
Moves a Dynamic QR Code to a different category.
The short URL,
Category changes are refused for static QR Codes and for static-only target categories — a static QR Code’s payload is baked into the printed pattern, so there is nothing to repoint.
PATCH https://api.scanova.io/qr/{qrid}/change-category/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
string
required
The QR Code’s
qrid.integer
required
Primary key of the destination category.
curl -X PATCH "https://api.scanova.io/qr/Qa1b2c3d4e5f6g7h8/change-category/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"category": 8
}'
This is destructive. On success the QR Code’s stored
info is wiped to an empty string and its previous content and media are discarded — the old category’s content cannot be recovered. It is not a metadata-only edit. Expect to immediately follow up with Update a QR Code to populate info for the new category.qrid, scan history, and design survive the change; only the content does not.
{
"qr_type": ["Edit category on static QR codes is not allowed."]
}
Related
- Update a QR Code — populate
infofor the new category afterwards. - List QR categories — pick a destination category that allows
dy. - Retrieve a QR Code — confirm the wiped content and new category.
- 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.
Path Parameters
The QR code's qrid — the opaque public identifier returned by the list endpoint, not the numeric id.
Response
Category changed — content has been wiped.
Was this page helpful?