curl -X DELETE "https://api.scanova.io/qr-assets/conditional-redirect-template/3/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
QR Assets
Delete a conditional redirect template
DELETE /qr-assets/conditional-redirect-template//
DELETE
/
qr-assets
/
conditional-redirect-template
/
{pk}
/
curl -X DELETE "https://api.scanova.io/qr-assets/conditional-redirect-template/3/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
Deletes a conditional redirect template owned by this account, on the Management API host (
A successful call returns
api.scanova.io), authenticated with your raw Management API key.
DELETE https://api.scanova.io/qr-assets/conditional-redirect-template/{pk}/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
integer
required
The template’s
id.curl -X DELETE "https://api.scanova.io/qr-assets/conditional-redirect-template/3/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
204 No Content. 404 if pk isn’t a template owned by this account. Deleting a template that’s already applied to a QR Code doesn’t remove the redirect rules from that QR Code — the rules were copied onto it when applied, not referenced live.
Related
- Retrieve a conditional redirect template — check before deleting.
- List conditional redirect templates — see what else is saved.
- Management API overview — the auth scheme and quota rules that apply to this endpoint.
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
Template deleted.
Was this page helpful?