curl --request GET \
--url 'https://api.scanova.io/web-tracking/sites/7/check-qr-attachment/?qr_id=501' \
--header 'Authorization: YOUR_API_KEY'
{ "is_attached": true }
Web Tracking
Check attachment
GET /web-tracking/sites//check-qr-attachment/
GET
/
web-tracking
/
sites
/
{site_id}
/
check-qr-attachment
/
curl --request GET \
--url 'https://api.scanova.io/web-tracking/sites/7/check-qr-attachment/?qr_id=501' \
--header 'Authorization: YOUR_API_KEY'
{ "is_attached": true }
Checks whether a tracking site has any QR Code attached at all, or (with
qr_id) whether one specific QR Code is attached to it — useful before calling Attach a QR to avoid a redundant 400 from the one-attachment-per-QR constraint.
Requires the account’s
CONVERSION_TRACKING quota.integer
required
Tracking site ID.
integer
A
dynamic_url_object ID to check specifically. Omit to check whether the site has any QR Code attached.curl --request GET \
--url 'https://api.scanova.io/web-tracking/sites/7/check-qr-attachment/?qr_id=501' \
--header 'Authorization: YOUR_API_KEY'
{ "is_attached": true }
404 if site_id isn’t owned by this account.
Related
- List / attach QR Codes
- Management API overview — the auth scheme and quota architecture this endpoint is part of.
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
Query Parameters
A dynamic_url_object id to check specifically; omit to check whether the site has any QR attached.
Response
Attachment status.
Was this page helpful?