> ## 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 your custom tags

> GET /tag/custom/

Lists custom tags created by the requesting account on the **Management API** host (`api.scanova.io`), authenticated with your raw Management API key — see the [overview](/api-reference/management-api/overview) if you haven't set that up yet.

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

This is a narrower list than [`GET /tag/list/`](/api-reference/management-api/tags/manage): 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.

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

<ResponseExample>
  ```json 200 theme={null}
  {
    "count": 2,
    "next": null,
    "previous": null,
    "results": [
      { "tag": "vip" },
      { "tag": "priority" }
    ]
  }
  ```
</ResponseExample>

Results are paginated. Note the shape here is intentionally minimal — just `tag` (the name) — unlike [`GET /tag/list/`](/api-reference/management-api/tags/manage)'s `{id, name}` rows.

## Related

* [Create a custom tag](/api-reference/management-api/tags/custom-create) — add to this list.
* [List tags](/api-reference/management-api/tags/manage) — the account's full tag directory, not just custom ones.
* [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/custom/
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/custom/:
    get:
      summary: List your custom tags
      description: >-
        Lists custom tags created by the requesting account (not the account's
        full tag list — see GET /tag/list/ for that). Paginated.
      operationId: listManagedCustomTags
      responses:
        '200':
          description: Paginated list of custom tags.
          content:
            application/json:
              example:
                count: 2
                next: null
                previous: null
                results:
                  - tag: vip
                  - tag: priority
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.

````