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

# Create a new toolkit

> Create a toolkit to group related tools (e.g. “Slack”, “CRM API”). You can then add tools to it and attach the toolkit to workflows and agents.



## OpenAPI

````yaml /api-reference/openapi.json post /api/v1/toolkits
openapi: 3.0.0
info:
  title: Flowra API (API Key Endpoints)
  description: >-
    **Flowra** is an AI-powered platform for building agents, workflows, and
    integrations.


    ### Capabilities

    - **Tools & Toolkits** – Define and group tools for agents and workflows.

    - **Workflows** – Orchestrate steps and automate processes.

    - **Triggers** – Schedule or event-based execution.

    - **Auth & Connections** – OAuth, API keys, and connected accounts.

    - **MCP** – Model Context Protocol server integration.

    - **Knowledge / RAG** – Add files and URLs for retrieval-augmented
    generation.


    ### Authentication

    Use the **x-api-key** header with a project API key to access endpoints that
    support API Key auth. Create and manage API keys in the dashboard under your
    project settings.


    Only endpoints that support API Key authentication via the @ApiKeyEnabled()
    decorator.


    Send x-api-key (required). On multi-tenant endpoints, optionally send
    x-username to act as an external user.


    Only endpoints that support API Key authentication via the @ApiKeyEnabled()
    decorator.


    Send x-api-key (required). On multi-tenant endpoints, optionally send
    x-username (defaults to the project’s default external user).
  version: '1.0'
  contact:
    name: Flowra
    url: https://flowra.dev
servers:
  - url: https://flowra.dev
    description: Flowra API
security: []
tags:
  - name: Users
    description: User profile
  - name: External Users
    description: End-user identities inside a project (x-username)
  - name: Auth Configs
    description: OAuth and API key configs for toolkits
  - name: Connected Accounts
    description: OAuth connected accounts and link creation
  - name: Toolkits
    description: List and search toolkits
  - name: Tools
    description: List, execute, and manage tools
  - name: Skills
    description: Browse, create, import, and install skills
  - name: Workflow & Agent
    description: Create, run, and inspect workflows and agents
  - name: Triggers
    description: Schedule and event-based trigger instances
  - name: Chat
    description: Threads and streaming agent runs
  - name: File
    description: Upload, list, and download files
  - name: Knowledge
    description: RAG knowledge collections
  - name: Table
    description: Collections and documents
  - name: Sandbox
    description: Ephemeral and durable code sandboxes
  - name: Browser
    description: Live browser sessions and view
  - name: LLM
    description: List AI models and generate completions
  - name: MCP
    description: MCP server management
paths:
  /api/v1/toolkits:
    post:
      tags:
        - Toolkits
      summary: Create a new toolkit
      description: >-
        Create a toolkit to group related tools (e.g. “Slack”, “CRM API”). You
        can then add tools to it and attach the toolkit to workflows and agents.
      operationId: ToolkitsController_createToolkit
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateToolkitDto'
      responses:
        '200':
          description: Toolkit created successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SuccessResponseDto'
        '201':
          description: ''
      security:
        - x-api-key: []
components:
  schemas:
    CreateToolkitDto:
      $ref: '#/components/schemas/CreateToolkitDto'
      type: object
      properties:
        slug:
          type: string
          minLength: 3
          maxLength: 100
          description: Toolkit slug identifier (unique)
          example: my-custom-toolkit
        name:
          type: string
          maxLength: 200
          description: Toolkit display name
          example: My Custom Toolkit
        description:
          type: string
          description: Toolkit description
          example: A comprehensive toolkit for custom integrations
        logo:
          type: string
          pattern: /^(https?:\/\/\S+|file:[0-9a-fA-F-]{36}|\/public\/\S+)$/
          description: >-
            Logo: https URL, synced global path (/public/...), or uploaded file
            reference file:<uuid>
          example: https://example.com/logo.png
        appUrl:
          type: string
          description: Application URL
          example: https://app.example.com
        authSchemes:
          description: Authentication schemes
          example:
            - OAUTH2
            - API_KEY
          type: array
          items:
            type: string
        providerManagedAuthSchemes:
          description: Provider-managed authentication schemes (e.g. Local or Composio)
          example:
            - OAUTH2
          type: array
          items:
            type: string
        noAuth:
          type: boolean
          default: false
          description: Whether this toolkit requires no authentication
          example: false
        version:
          type: string
          default: 1.0.0
          description: Toolkit version
          example: 1.0.0
        popularityScore:
          type: number
          minimum: 0
          description: Popularity score (ordering / ranking)
          example: 0
          default: 0
        categories:
          description: Toolkit categories
          type: array
          items:
            type: object
        baseUrl:
          type: string
          description: Base URL
          example: https://api.example.com
        authConfigDetails:
          description: Auth config details
          type: array
          items:
            $ref: '#/components/schemas/AuthConfigDetailsDto'
        getCurrentUserEndpoint:
          type: string
          description: Get current user endpoint path
          example: /api/user
      required:
        - slug
        - name
        - description
    SuccessResponseDto:
      $ref: '#/components/schemas/SuccessResponseDto'
      type: object
      properties:
        success:
          type: boolean
          description: Success status
          example: true
        message:
          type: string
          description: Success message
          example: Operation completed successfully
        data:
          type: object
          description: Response data
      required:
        - success
        - message
        - data
  securitySchemes:
    x-api-key:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        Project API key. Create and manage keys in the dashboard under Project →
        API Keys. Send as header: x-api-key: <your-key>

````