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

# List Folders

> Folders are where an assessment is filed: single-parent and nestable.
They are the structure the Edpire library UI shows, and the only
organisational object in the API.

Edpire owns the content and the results; how those assessments map onto
*your* product — courses, topics, levels — is yours to model, in your own
database, against our assessment IDs. Browse folders to pick content;
keep your own groupings on your side, where you know when they change.




## OpenAPI

````yaml GET /folders
openapi: 3.1.0
info:
  title: Edpire API
  description: >
    Edpire is a headless assessment engine. This API lets you manage
    assessments,

    submit answers for grading, retrieve results, organise them into folders,
    and configure

    webhooks for real-time notifications.


    All responses use a consistent envelope: `{ data, error, meta }`.
  version: 1.0.0
  contact:
    name: Edpire Support
    url: https://edpire.com
  license:
    name: Proprietary
servers:
  - url: https://edpire.com/api/v1
    description: Production
security:
  - BearerAuth: []
tags:
  - name: Assessments
    description: Create, list, update, publish, and grade assessments
  - name: Submissions
    description: Retrieve submission details
  - name: Learners
    description: Query learner results
  - name: Webhooks
    description: Register and manage webhook endpoints
  - name: Embed
    description: Mint tokens and load assessments for browser-side rendering
  - name: Folders
    description: Nestable structure for filing assessments
  - name: Authoring
    description: Hand an author into the Edpire builder from your own admin
paths:
  /folders:
    get:
      tags:
        - Folders
      summary: List folders
      description: >
        Folders are where an assessment is filed: single-parent and nestable.

        They are the structure the Edpire library UI shows, and the only

        organisational object in the API.


        Edpire owns the content and the results; how those assessments map onto

        *your* product — courses, topics, levels — is yours to model, in your
        own

        database, against our assessment IDs. Browse folders to pick content;

        keep your own groupings on your side, where you know when they change.
      operationId: listFolders
      parameters:
        - name: parent_id
          in: query
          description: >-
            Children of this folder. Omit, or pass `null`, for top-level
            folders.
          schema:
            type: string
      responses:
        '200':
          description: Folders at the requested level
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/Folder'
                  error:
                    type: 'null'
                  meta:
                    type: 'null'
components:
  schemas:
    Folder:
      type: object
      properties:
        id:
          type: string
          format: uuid
        name:
          type: string
        slug:
          type: string
        parent_folder_id:
          type: string
          format: uuid
          nullable: true
        assessment_count:
          type: integer
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: >
        API key starting with `edp_live_`. Pass via `Authorization: Bearer
        edp_live_xxx`.


        Scopes: `read:assessments`, `write:assessments`, `read:results`,
        `write:submissions`.

````