Skip to main content
PUT
Retrieves, updates, or deletes a single QR Code on api.scanova.io, authenticated with your raw API key.
​
string
required
The QR Code’s qrid (e.g. QR7K9M2XN) — the human-readable identifier returned by GET /qr/, not the numeric id.
The legacy /qrcode/{qrid}/ path is also still reachable, kept for backward compatibility — both paths resolve to the identical view and behavior. This reference documents the canonical /qr/{qrid}/ path (under the same prefix as the list/create endpoint).
Both PUT and PATCH are supported (PUT for a full replace, PATCH for a partial update) and accept the same field set documented for Create a QR Code. A successful update returns 200 OK with the updated detail representation shown above.

​
Scope and errors

Every method here only operates on QR Codes owned by the account the key belongs to — requesting a qrid 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.
  • Retrieve — the other operation on this same endpoint.
  • Delete — the other operation on this same endpoint.
  • List QR Codes — find a qrid to operate on here, or the full field set this endpoint’s update accepts.
  • Create a QR Code — find a qrid to operate on here, or the full field set this endpoint’s update accepts.
  • Download a QR Code image — render this QR Code as an image file.
  • List trashed QR Codes — where a QR Code lands after DELETE here.

Authorizations

​
Authorization
string
header
required

Send your Management API key as the raw value of the Authorization header — no "Bearer " or "Token " prefix, and no other characters. Example: Authorization: YOUR_API_KEY. 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

​
qrid
string
required

Response

200

QR code updated