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

# Connect an account

> Connects the account, either outright or by returning a URL to authorise in a browser — `connected` says which happened. API-key apps are connected in this one call; OAuth apps need the round trip. A 400 with code `INTEGRATION_SETUP_REQUIRED` names the fields still missing (see GET /integrations/:app/auth). Once connected, call POST /integrations/:app/servers to build the tool server.



## OpenAPI

````yaml POST /v1/integrations/{app}/connect
openapi: 3.0.0
info:
  title: Devic.ai Public API
  description: >-
    Devic.ai is an AI platform that allows you to create, manage, and use AI
    agents for various tasks.
  version: 1.0.0
  contact:
    name: Devic.ai Support
    url: https://devic.ai
  x-logo:
    url: https://devic.ai/logo.png
    altText: Devic.ai Logo
  x-summary: Public API for interacting with Devic.ai platform
servers:
  - url: https://api.devic.ai
    description: Production server
  - url: https://staging-api.devic.ai
    description: Staging server
security:
  - bearerAuth: []
tags:
  - name: Projects
    description: Group agents, assistants, documents and costs into projects
  - name: Documents
    description: >-
      Knowledge base documents: create, version, attach and index markdown
      content for RAG
  - name: Document Folders
    description: Organise knowledge base documents into folders and attach them in bulk
  - name: Files
    description: Upload files and obtain shareable download URLs to attach to messages
  - name: Agents
    description: Endpoints related to AI agents and their operations
  - name: Assistants
    description: Endpoints for interacting with assistants and their specializations
  - name: Tool Servers
    description: Endpoints for managing tool servers and their tool definitions
  - name: Health
    description: API health check endpoints
  - name: Documentation
    description: Endpoints for retrieving markdown documentation
  - name: Integrations
    description: Connect third-party apps and turn them into tools
  - name: Triggers
    description: Start an agent or an assistant from an app event
  - name: Tenant Integrations
    description: Apps that each end user connects for themselves
  - name: Memory
    description: What an assistant remembers between conversations
  - name: Skills
    description: Reusable instruction packs for agents and assistants
  - name: Speech to Text
    description: Audio transcription
  - name: Tenants
    description: Tenants, subtenants and their usage
  - name: MCP Gateway
    description: One MCP endpoint over many servers, with visibility per user
  - name: Tenant Sessions
    description: Tokens that prove which end user is calling
paths:
  /v1/integrations/{app}/connect:
    post:
      tags:
        - Integrations
      summary: Connect an account
      description: >-
        Connects the account, either outright or by returning a URL to authorise
        in a browser — `connected` says which happened. API-key apps are
        connected in this one call; OAuth apps need the round trip. A 400 with
        code `INTEGRATION_SETUP_REQUIRED` names the fields still missing (see
        GET /integrations/:app/auth). Once connected, call POST
        /integrations/:app/servers to build the tool server.
      operationId: connectAppAccount
      parameters:
        - name: app
          required: true
          in: path
          description: App slug
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ConnectIntegrationDto'
      responses:
        '201':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ConnectIntegrationResponseDto'
        '401':
          description: Unauthorized - Invalid or missing token
        '429':
          description: Too Many Requests - Rate limit exceeded
        '500':
          description: Internal Server Error
      security:
        - bearerAuth: []
components:
  schemas:
    ConnectIntegrationDto:
      type: object
      properties:
        authScheme:
          type: string
          description: >-
            Which scheme to connect through, from GET /integrations/:app/auth.
            Defaults to the one asking for least setup
          example: API_KEY
        appCredentials:
          type: object
          description: >-
            Credentials of your own application with the provider, keyed by the
            scheme's appFields. Needed once per workspace for apps the
            integration provider holds no credentials for; ignored afterwards
          example:
            client_id: …
            client_secret: …
        accountFields:
          type: object
          description: >-
            What this account supplies, keyed by the scheme's accountFields — an
            API key, the subdomain of your instance
          example:
            generic_api_key: pplx-…
    ConnectIntegrationResponseDto:
      type: object
      properties:
        connected:
          type: boolean
          description: >-
            True when the account is connected already — API-key apps have
            nothing to authorise, so no browser is involved
        authorizationUrl:
          type: string
          description: >-
            Open this URL in a browser to authorise the account. Absent when
            connected is already true
      required:
        - connected
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Use JWT token for authentication

````