> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanova.io/llms.txt
> Use this file to discover all available pages before exploring further.

# List tags visible to your shared-user role

> GET /tag/shared/

Lists the tags a shared user's role has been granted visibility into, on the **Management API** host (`api.scanova.io`), authenticated with your raw Management API key.

```
GET https://api.scanova.io/tag/shared/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<RequestExample>
  ```bash cURL theme={null}
  curl "https://api.scanova.io/tag/shared/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  [
    { "id": 12, "name": "vip" },
    { "id": 14, "name": "east-region" }
  ]
  ```
</ResponseExample>

Not paginated — returns a plain array.

## Only meaningful for a shared user's key

This endpoint only makes sense for a Management API key created on behalf of a shared user whose account has [tag-based permission scoping](/team/roles-and-permissions) enabled. A key belonging to the account owner (who isn't scoped by tags in the first place) returns `400` with `{"error": ["Request user is not a shared user"]}`.

## Related

* [List tags](/api-reference/management-api/tags/manage) — the unscoped equivalent, for the account owner.
* [List/detach tags attached by a shared user](/api-reference/management-api/tags/attached-list) — a different view: what one teammate has tagged, rather than what they can see.
* [Roles & permissions](/team/roles-and-permissions) — how tag-based permission scoping works from the dashboard side.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota rules that apply to this endpoint.


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /tag/shared/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    api.scanova.io (QR codes, folders, tags, leads, forms, analytics, plans,
    shared users & roles), plus the token-creation and usage-stats endpoints
    used to authenticate against it. Every path and request/response shape below
    was verified live against a real API key and the actual running backend
    (Phase 7, 2026-08-16) — not guessed from reading urls.py alone.
  version: 2.0.0
servers:
  - url: https://api.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /tag/shared/:
    get:
      summary: List tags visible to your shared-user role
      description: >-
        Lists the tags a shared user's role has been granted visibility into
        (via tag-based permission scoping). Only meaningful for a Management API
        key created on behalf of a shared user — a key belonging to the account
        owner returns 400, since the owner isn't scoped by tag permissions in
        the first place.
      operationId: listManagedSharedTags
      responses:
        '200':
          description: Tags visible to this shared user. Not paginated.
          content:
            application/json:
              example:
                - id: 12
                  name: vip
                - id: 14
                  name: east-region
        '400':
          description: The requesting key does not belong to a shared user.
components:
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        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.

````