curl --request DELETE \
--url 'https://api.scanova.io/web-tracking/sites/qrs/2/' \
--header 'Authorization: YOUR_API_KEY'
{
"id": 2,
"site": {
"id": 7,
"site_id": "aZ3kP9...64-char-random-id",
"name": "Marketing site",
"is_active": true,
"verified_on": "2026-09-05T09:00:00+05:30",
"is_verified": true,
"created": "2026-09-01T10:00:00+05:30",
"modified": "2026-09-09T08:10:00+05:30"
},
"dynamic_url_object": 501,
"is_active": true,
"created": "2026-09-09T08:15:00+05:30",
"modified": "2026-09-09T08:15:00+05:30"
}Web Tracking
Retrieve / update / detach a QR
GET, PATCH, DELETE /web-tracking/sites/qrs//
GET
/
web-tracking
/
sites
/
qrs
/
{pk}
/
curl --request DELETE \
--url 'https://api.scanova.io/web-tracking/sites/qrs/2/' \
--header 'Authorization: YOUR_API_KEY'
{
"id": 2,
"site": {
"id": 7,
"site_id": "aZ3kP9...64-char-random-id",
"name": "Marketing site",
"is_active": true,
"verified_on": "2026-09-05T09:00:00+05:30",
"is_verified": true,
"created": "2026-09-01T10:00:00+05:30",
"modified": "2026-09-09T08:10:00+05:30"
},
"dynamic_url_object": 501,
"is_active": true,
"created": "2026-09-09T08:15:00+05:30",
"modified": "2026-09-09T08:15:00+05:30"
}Manages a single tracking-site/QR attachment.
DELETE detaches the QR Code from the tracking site — it does not delete the QR Code itself.
Unlike every other endpoint in this module, the path here is
sites/qrs/{pk}/ rather than sites/{site_id}/qrs/{pk}/ — the attachment id alone identifies the record, scoped to your account rather than to a specific site in the URL.integer
required
Attachment ID, from List QR attachments.
boolean
Pause/resume the attachment (PATCH) without detaching it.
curl --request DELETE \
--url 'https://api.scanova.io/web-tracking/sites/qrs/2/' \
--header 'Authorization: YOUR_API_KEY'
204 on detach, 404 if pk doesn’t belong to a site owned by this account.
Related
- List / attach QR Codes
- Check attachment
- 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
Response
One QR attachment.
Was this page helpful?