Skip to main content
PATCH
Repoints a Dynamic QR Code’s short URL to a new slug.
string
required
The QR Code’s qrid.
string
required
The new slug. Must match ^[a-zA-Z0-9\-_]{3,50}$ and be free on this QR Code’s domain.
Every QR Code already printed with the previous slug stops working. The old short URL is not kept as a redirect. The API returns this as an explicit warning field in the success response — surface it to the user rather than swallowing it. Only change a slug for a QR Code that has not been distributed yet.
A successful change marks the QR Code as using a custom hash and invalidates the landing app’s cache for both the old and the new slug, so the switch takes effect immediately. 400 means the slug is malformed; 409 means it is already taken on this domain.

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: 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

qrid
string
required

The QR code's qrid — the opaque public identifier returned by the list endpoint, not the numeric id.

Response

Slug changed.