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

# Retrieve a folder

> GET /folder/{id}/

Fetches a single folder by ID.

<Note>
  Requires a Management API key, sent as the raw `Authorization` header value. Reads have no additional quota/permission gate. See the [Management API overview](/api-reference/management-api/overview) for authentication details.
</Note>

<ParamField path="id" type="integer" required>
  Folder ID, from [List folders](/api-reference/management-api/folders/list).
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl --request GET \
    --url 'https://api.scanova.io/folder/42/' \
    --header 'Authorization: YOUR_API_KEY'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": 42,
    "name": "Marketing Campaigns",
    "color": "#4F6BF4",
    "created_by": 1029,
    "folder_type": "qr",
    "qr_codes_count": 12,
    "created": "2026-09-01T10:00:00+05:30",
    "updated": "2026-09-05T12:30:00+05:30"
  }
  ```
</ResponseExample>

A folder belonging to a different account returns `404`, not `403` — this endpoint never reveals whether an ID belongs to someone else.

## Related

* [List folders](/api-reference/management-api/folders/list) — find a folder's `id`.
* [Update a folder](/api-reference/management-api/folders/update) — rename or recolor it.
* [Delete a folder](/api-reference/management-api/folders/delete) — remove it.
* [List QR Codes in a folder](/api-reference/management-api/folders/qr-codes) — the QR Codes assigned to it.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota architecture this endpoint is part of.


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /folder/{id}/
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:
  /folder/{id}/:
    get:
      summary: Retrieve a folder
      operationId: getManagedFolder
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: integer
      responses:
        '200':
          description: One folder.
          content:
            application/json:
              example:
                id: 42
                name: Marketing Campaigns
                color: '#4F6BF4'
                created_by: 1029
                folder_type: qr
                qr_codes_count: 12
                created: '2026-09-01T10:00:00+05:30'
                updated: '2026-09-05T12:30:00+05:30'
        '404':
          description: No folder with this id owned by this account.
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.

````