curl "https://api.scanova.io/tag/shared/" \
-H "Authorization: YOUR_API_KEY"
[
{ "id": 12, "name": "vip" },
{ "id": 14, "name": "east-region" }
]
Folders & Tags
List tags visible to your shared-user role
GET /tag/shared/
GET
/
tag
/
shared
/
curl "https://api.scanova.io/tag/shared/" \
-H "Authorization: YOUR_API_KEY"
[
{ "id": 12, "name": "vip" },
{ "id": 14, "name": "east-region" }
]
Lists the tags a shared user’s role has been granted visibility into, on
Not paginated — returns a plain array.
api.scanova.io, authenticated with your raw API key.
GET https://api.scanova.io/tag/shared/
Authorization: YOUR_API_KEY
curl "https://api.scanova.io/tag/shared/" \
-H "Authorization: YOUR_API_KEY"
[
{ "id": 12, "name": "vip" },
{ "id": 14, "name": "east-region" }
]
Only meaningful for a shared user’s key
This endpoint only makes sense for an API key created on behalf of a shared user whose account has tag-based permission scoping enabled. A key belonging to the account owner (who isn’t scoped by tags in the first place) returns400 with {"error": ["Request user is not a shared user"]}.
Related
- List tags — the unscoped equivalent, for the account owner.
- List/detach tags attached by a shared user — a different view: what one teammate has tagged, rather than what they can see.
- Roles & permissions — how tag-based permission scoping works from the dashboard side.
- 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
Tags visible to this shared user. Not paginated.
Was this page helpful?