curl "https://api.scanova.io/tag/custom/" \
-H "Authorization: YOUR_API_KEY"
{
"count": 2,
"next": null,
"previous": null,
"results": [
{ "tag": "vip" },
{ "tag": "priority" }
]
}
Folders & Tags
List your custom tags
GET /tag/custom/
GET
/
tag
/
custom
/
curl "https://api.scanova.io/tag/custom/" \
-H "Authorization: YOUR_API_KEY"
{
"count": 2,
"next": null,
"previous": null,
"results": [
{ "tag": "vip" },
{ "tag": "priority" }
]
}
Lists custom tags created by the requesting account on
This is a narrower list than
Results are paginated. Note the shape here is intentionally minimal — just
api.scanova.io, authenticated with your raw API key — see the overview if you haven’t set that up yet.
GET https://api.scanova.io/tag/custom/
Authorization: YOUR_API_KEY
GET /tag/list/: that endpoint returns every tag visible to the account (including tags attached implicitly via QR Codes), while this one returns only the tags this account explicitly created through the custom-tag flow.
curl "https://api.scanova.io/tag/custom/" \
-H "Authorization: YOUR_API_KEY"
{
"count": 2,
"next": null,
"previous": null,
"results": [
{ "tag": "vip" },
{ "tag": "priority" }
]
}
tag (the name) — unlike GET /tag/list/’s {id, name} rows.
Related
- Create a custom tag — add to this list.
- List tags — the account’s full tag directory, not just custom ones.
- 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: YOUR_API_KEY. 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.
Response
200 - application/json
Paginated list of custom tags.
Was this page helpful?