Ditto (dittowords.com) Component Folders API

The Component Folders API from Ditto (dittowords.com) — 1 operation(s) for component folders.

Operations 4

GET /componentFolders Fetch component folders #
POST /componentFolders Create component folders #
PATCH /componentFolders Update component folders #
DELETE /componentFolders Delete component folders #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/dittowords:dittowords-component-folders-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

dittowords-component-folders-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  version: 1.0.0
  title: Ditto Component Folders API
  description: Programmatically read and write data in your Ditto workspace.
servers:
- url: https://api.dittowords.com/v2
tags:
- name: Component Folders
paths:
  /componentFolders:
    get:
      tags:
      - Component Folders
      description: 'Returns all folders in your component library, with their developer IDs, names, and parent folder (by developer ID; null when the folder sits directly under the library root).


        Folders are a separate namespace from project folders.'
      summary: Fetch component folders
      security:
      - ApiKeyAuth: []
      responses:
        '200':
          description: Returns an array of all folders in the component library
          content:
            application/json:
              schema:
                type: array
                items:
                  type: object
                  properties:
                    id:
                      type: string
                      description: The developer ID of the folder
                    name:
                      type: string
                      description: The name of the folder
                    parentId:
                      type:
                      - string
                      - 'null'
                      description: Developer ID of the parent folder, or null if the folder sits directly under the library root
                  required:
                  - id
                  - name
                  - parentId
                example:
                - id: inputs
                  name: Inputs
                  parentId: null
                - id: text-fields
                  name: Text Fields
                  parentId: inputs
      operationId: getComponentFolders
      x-operation-id-source: derived
    post:
      tags:
      - Component Folders
      description: Creates one or more folders in the component library.
      summary: Create component folders
      security:
      - ApiKeyAuth: []
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                folders:
                  type: array
                  items:
                    type: object
                    properties:
                      name:
                        type: string
                        description: The name of the new folder
                      developerId:
                        type: string
                        description: Optional preconfigured developer ID for the folder. Must be unique within the workspace. If omitted, one is generated automatically from the name.
                      parentId:
                        type: string
                        description: Developer ID of the parent folder to nest the new folder inside (from list_component_folders). Omit or set to "root" to create the folder at the library root.
                    required:
                    - name
                  minItems: 1
                  description: Array of new folders to create
              required:
              - folders
              example:
                folders:
                - name: Inputs
                - name: Text Fields
                  developerId: text-fields
                  parentId: inputs
      responses:
        '200':
          description: Returns the developer IDs of the created folders, in request order
          content:
            application/json:
              schema:
                type: object
                properties:
                  developerIds:
                    type: array
                    items:
                      type: string
                    description: Array of developer IDs for the created folders, in request order
                required:
                - developerIds
                example:
                  developerIds:
                  - inputs
                  - text-fields
        '400':
          description: 'Returned when the request body fails validation. Common causes include: a parentId not matching any existing folder in the workspace.'
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    description: Error message describing the validation failure
                required:
                - message
              example:
                message: Folder id not found
        '409':
          description: Returned when a supplied developer ID already exists in the workspace
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    description: Error message describing the conflict
                required:
                - message
              example:
                message: already exists in workspace
      operationId: postComponentFolders
      x-operation-id-source: derived
    patch:
      tags:
      - Component Folders
      description: 'Updates a set of component folders.


        Each folder is identified by its developer ID. Only provided fields are modified — omitted fields remain unchanged.'
      summary: Update component folders
      security:
      - ApiKeyAuth: []
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                updates:
                  type: array
                  items:
                    type: object
                    properties:
                      developerId:
                        type: string
                        description: The folder's current developer ID
                      name:
                        type: string
                        description: New name for the folder. If not provided, name remains unchanged.
                      parentId:
                        type:
                        - string
                        - 'null'
                        description: Developer ID of the folder to move this folder into. Provide null or "root" to move it to the library root. Omit to leave the folder's parent unchanged.
                      newDeveloperId:
                        type: string
                        description: A new developer ID for this folder. Must be unique within the workspace. Can be set alongside a name or parent change in the same update object.
                    required:
                    - developerId
                  minItems: 1
                  description: Array of updates to folders
              required:
              - updates
              example:
                updates:
                - developerId: text-fields
                  name: Inputs — Text Fields
            examples:
              rename_folder:
                summary: Rename a folder
                value:
                  updates:
                  - developerId: text-fields
                    name: Inputs — Text Fields
              move_folder:
                summary: Move a folder to a new parent
                value:
                  updates:
                  - developerId: text-fields
                    parentId: inputs
              move_to_root:
                summary: Move a folder to the library root
                value:
                  updates:
                  - developerId: text-fields
                    parentId: null
              update_developer_id:
                summary: Change a folder's developer ID
                value:
                  updates:
                  - developerId: text-fields
                    newDeveloperId: input-fields
      responses:
        '200':
          description: Returns success status of the update operation
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    description: Indicates whether the update was successful
                required:
                - success
                example:
                  success: true
        '400':
          description: 'Returned when the request body fails validation. Common causes include: a developer ID that does not match any existing folder in the workspace, a parentId that does not match any existing folder, or a parent move that would create a circular folder hierarchy.'
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    description: Error message describing the validation failure
                required:
                - message
              example:
                message: Folder id not found
        '409':
          description: Returned when a supplied newDeveloperId already exists in the workspace
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    description: Error message describing the conflict
                required:
                - message
              example:
                message: already exists in workspace
      operationId: patchComponentFolders
      x-operation-id-source: derived
    delete:
      tags:
      - Component Folders
      description: Deletes folders from the component library.
      summary: Delete component folders
      security:
      - ApiKeyAuth: []
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                developerIds:
                  type: array
                  items:
                    type: string
                  minItems: 1
                  description: Developer IDs of the folders to delete. Components and subfolders inside a deleted folder are moved to its parent folder (or the library root), not deleted.
              required:
              - developerIds
              example:
                developerIds:
                - text-fields
      responses:
        '200':
          description: Returns success status of the deletion operation
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    description: Indicates whether the deletion was successful
                required:
                - success
                example:
                  success: true
        '400':
          description: Returned when a developer ID does not match any existing folder in the workspace
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    description: Error message describing the validation failure
                required:
                - message
              example:
                message: Folder id not found
      operationId: deleteComponentFolders
      x-operation-id-source: derived
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: Authorization