curl -X PUT "https://api.scanova.io/qr/multi/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"qrids": [
"Qa1b2c3d4e5f6g7h8",
"Qb2c3d4e5f6g7h8i9"
],
"is_active": false
}'
QR Codes
Bulk-update QR Code fields
PUT /qr/multi/
PUT
/
qr
/
multi
/
curl -X PUT "https://api.scanova.io/qr/multi/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"qrids": [
"Qa1b2c3d4e5f6g7h8",
"Qb2c3d4e5f6g7h8i9"
],
"is_active": false
}'
Sets the same field values across many QR Codes at once.
Any remaining top-level keys are applied as raw QR-code field overrides —
Returns
PUT https://api.scanova.io/qr/multi/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
array
The
qrid values to update.boolean
default:"false"
Apply to every QR Code the account owns, ignoring
qrids.{"is_active": false} in the example below.
curl -X PUT "https://api.scanova.io/qr/multi/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{
"qrids": [
"Qa1b2c3d4e5f6g7h8",
"Qb2c3d4e5f6g7h8i9"
],
"is_active": false
}'
204 No Content.
This is a low-level field-set that bypasses per-category schema validation entirely for the fields it writes. It does not carry the same safety as Update a QR Code — a value that endpoint would reject can be written here, leaving content that fails validation the next time it is edited or published. Use it for simple flags across a selection, not for content.
Toggling
is_active has a side effect beyond the flag itself: it clears or re-derives expire_on on the related dynamic URL objects, so a previously-expired QR Code reactivated this way does not immediately re-expire.Related
- Update a QR Code — the validated, single-QR update path.
- Copy a QR Code — the
POSToperation on this same path. - Delete many QR Codes — the bulk delete equivalent.
- 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
Fields applied.
Was this page helpful?