curl --request DELETE \
--url 'https://api.scanova.io/folder/42/' \
--header 'Authorization: YOUR_API_KEY'
curl --request DELETE \
--url 'https://api.scanova.io/folder/42/?move_to_uncategorized=true' \
--header 'Authorization: YOUR_API_KEY'
curl --request DELETE \
--url 'https://api.scanova.io/folder/42/?delete_permanently=true' \
--header 'Authorization: YOUR_API_KEY'
{
"message": "Folder and associated QR codes deleted."
}Folders & Tags
Delete a folder
DELETE /folder//
DELETE
/
folder
/
{id}
/
curl --request DELETE \
--url 'https://api.scanova.io/folder/42/' \
--header 'Authorization: YOUR_API_KEY'
curl --request DELETE \
--url 'https://api.scanova.io/folder/42/?move_to_uncategorized=true' \
--header 'Authorization: YOUR_API_KEY'
curl --request DELETE \
--url 'https://api.scanova.io/folder/42/?delete_permanently=true' \
--header 'Authorization: YOUR_API_KEY'
{
"message": "Folder and associated QR codes deleted."
}Deletes a folder. A query parameter controls what happens to the QR Codes inside it — there is no default “safe” behavior beyond leaving those three modes explicit, so choose one deliberately.
Requires the account’s
FOLDER_MANAGEMENT quota and the FOLDER_CAN_CREATE_AND_MANAGE permission. See the Management API overview for authentication details.integer
required
Folder ID.
boolean
If
true, the folder is deleted and its QR Codes are unassigned (moved to “Uncategorized”) rather than deleted.boolean
If
true, every QR Code in the folder owned by your account is permanently deleted along with the folder. QR Codes in the same folder that belong to a different user on a shared account are not deleted — only their folder assignment is cleared.Delete modes
| Query string | Behavior | Response body |
|---|---|---|
| (none) | Folder is deleted; its QR Codes’ folder assignment is cleared. | 204, empty. |
?move_to_uncategorized=true | Same as above, worded explicitly. | 204 with {"message": "Folder deleted and QR codes moved to Uncategorized."} |
?delete_permanently=true | Folder and its QR Codes (owned by you) are permanently deleted. | 204 with {"message": "Folder and associated QR codes deleted."} |
A
204 response normally has no body — the two modes above that pass a query parameter are an exception and do return a JSON body despite the 204 status. Some HTTP clients silently discard a 204 body; don’t rely on it if you can’t confirm yours reads it. If you send both move_to_uncategorized=true and delete_permanently=true at once, move_to_uncategorized wins.curl --request DELETE \
--url 'https://api.scanova.io/folder/42/' \
--header 'Authorization: YOUR_API_KEY'
curl --request DELETE \
--url 'https://api.scanova.io/folder/42/?move_to_uncategorized=true' \
--header 'Authorization: YOUR_API_KEY'
curl --request DELETE \
--url 'https://api.scanova.io/folder/42/?delete_permanently=true' \
--header 'Authorization: YOUR_API_KEY'
404 if id isn’t owned by this account.
Related
- Retrieve a folder — check what’s in it first.
- List QR Codes in a folder — review contents before an irreversible
delete_permanently. - 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
Unassign the folder's QR codes (move to Uncategorized) instead of leaving them as-is.
Permanently delete the folder's QR codes (owned by this account) along with the folder.
Response
Folder deleted. A JSON body is included only when move_to_uncategorized or delete_permanently is set.
Was this page helpful?