curl -X DELETE "https://management.scanova.io/qrcode/QR7K9M2XN/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
Management API — QR Codes
Delete
DELETE /qrcode//
DELETE
/
qrcode
/
{qrid}
/
curl -X DELETE "https://management.scanova.io/qrcode/QR7K9M2XN/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
Retrieves, updates, or deletes a single QR code on the Management API host (
management.scanova.io), authenticated with your raw Management API key.
GET https://management.scanova.io/qrcode/{qrid}/
PUT https://management.scanova.io/qrcode/{qrid}/
PATCH https://management.scanova.io/qrcode/{qrid}/
DELETE https://management.scanova.io/qrcode/{qrid}/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
string
required
The QR code’s
qrid (e.g. QR7K9M2XN) — the human-readable identifier returned by GET /qr/, not the numeric id.This same view is also reachable at
/qr/{qrid}/ (i.e. under the same path prefix as the list/create endpoint) — both paths resolve to the identical view and behavior. This reference documents /qrcode/{qrid}/ since that’s the path verified for this doc set, but either works.DELETE soft-deletes the QR code — it moves to the trash (see QR trash) rather than being permanently removed, and returns 204 No Content.
curl -X DELETE "https://management.scanova.io/qrcode/QR7K9M2XN/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
Scope and errors
Every method here only operates on QR codes owned by the account the key belongs to — requesting aqrid you don’t own (or that doesn’t exist) returns 404, not 403, so you can’t use this endpoint to probe for the existence of other accounts’ QR codes.
Related
- Retrieve — the other operation on this same endpoint.
- Update — the other operation on this same endpoint.
- List QR codes — find a
qridto delete here. - Download a QR code image — render this QR code as an image file.
- List trashed QR codes — where a QR code lands after
DELETEhere.
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. management.scanova.io) — the same key sent to the regular API host will not authenticate.
Path Parameters
Response
204
QR code deleted
Was this page helpful?
⌘I