> ## 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.

# Obtener recuentos de uso de un tema

> GET /theme/{slug}/usage/

Obtiene recuentos de lo que actualmente usa un tema, en el host de la **API de gestión** (`api.scanova.io`), autenticado con su clave de API de gestión sin procesar.

```
GET https://api.scanova.io/theme/{slug}/usage/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField path="slug" type="string" required>
  El `slug` del tema.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl "https://api.scanova.io/theme/user-42-ocean-breeze-a1b2c3/usage/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "qr_count": 12,
    "form_count": 3
  }
  ```
</ResponseExample>

Cuenta solo códigos QR y formularios activos (no eliminados) — útil para comprobar antes de [Actualizar un tema](/es/api-reference/management-api/theme-manager/theme-update) o de eliminar la cuenta propietaria de un tema, ya que las ediciones pueden afectar a todo lo que lo usa.

## Relacionado

* [Actualizar un tema](/es/api-reference/management-api/theme-manager/theme-update) — la opción `clear_conflicting_overrides` es más relevante cuando este recuento no es cero.
* [Obtener un tema](/es/api-reference/management-api/theme-manager/theme-retrieve) — ver el tema en sí.
* [Resumen de la API de gestión](/es/api-reference/management-api/overview) — el esquema de autenticación y las reglas de cuota aplicables a este endpoint.


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /theme/{slug}/usage/
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:
  /theme/{slug}/usage/:
    get:
      summary: Get theme usage counts
      description: >-
        Counts of active (non-deleted) QR codes and forms currently using this
        theme.
      operationId: getThemeUsage
      parameters:
        - name: slug
          in: path
          required: true
          schema:
            type: string
      responses:
        '200':
          description: Usage counts.
          content:
            application/json:
              example:
                qr_count: 12
                form_count: 3
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.

````