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

# List direct messages

> Your private conversations, newest activity first. They are account-wide (any two people of the account, whatever workspaces they share) and live in one hidden space of the account, never listed as a workspace. Read and write them with the thread endpoints using the returned `workspaceId`. The account integration (an API key without `X-Devic-User`) has none: `403 DIRECT_MESSAGES_REQUIRE_USER`.



## OpenAPI

````yaml GET /v1/workspaces/direct-messages
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: Environments
    description: >-
      The machine an agent works on and everything it may reach: sandbox,
      snapshot, knowledge, tools and encrypted variables
  - name: Sandboxes
    description: >-
      Start a real Linux machine on an environment, run commands and files on
      it, and save its snapshot
  - 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
  - name: Workspaces
    description: Shared spaces where people and assistants work in threads
  - name: Workspace Threads
    description: Threads, messages, read state and assistant runs
  - name: Workspace Files
    description: Files and documents of workspaces and threads
  - name: Workspace Configuration
    description: Members, assistants, knowledge, skills and rules
  - name: Workspace Memory
    description: Core memory of the assistants of a workspace
  - name: Workspace Automations
    description: Scheduled and triggered work of a workspace
  - name: Workspace Integrations
    description: >-
      App accounts a workspace can use, and connecting a new one through an
      authorization link.
paths:
  /v1/workspaces/direct-messages:
    get:
      tags:
        - Workspace Threads
      summary: List direct messages
      description: >-
        Your private conversations, newest activity first. They are account-wide
        (any two people of the account, whatever workspaces they share) and live
        in one hidden space of the account, never listed as a workspace. Read
        and write them with the thread endpoints using the returned
        `workspaceId`. The account integration (an API key without
        `X-Devic-User`) has none: `403 DIRECT_MESSAGES_REQUIRE_USER`.
      operationId: listWorkspaceDirectMessages
      parameters:
        - $ref: '#/components/parameters/XDevicUser'
      responses:
        '200':
          description: 'Success — wrapped as `{ success: true, data }`'
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    example: true
                  data:
                    $ref: '#/components/schemas/WorkspaceDirectMessages'
        '400':
          description: Bad request — invalid or inconsistent payload
        '401':
          description: Unauthorized — missing or invalid credential
        '403':
          description: >-
            Forbidden — not a member, not enough workspace permission, or acting
            for someone the credential cannot act for
        '404':
          description: Not found
      security:
        - bearerAuth: []
components:
  parameters:
    XDevicUser:
      name: X-Devic-User
      in: header
      required: false
      schema:
        type: string
      description: >-
        Only with an **API key**: the userUID or email of a person of the key's
        account to act as, with that person's permissions. Without it, an API
        key acts as the account integration ("API"), which sees shared
        workspaces only. A person's token cannot name someone else.
  schemas:
    WorkspaceDirectMessages:
      type: object
      properties:
        workspaceId:
          type: string
          nullable: true
          description: >-
            The account's private-conversation space: use it as `{wid}` in the
            thread endpoints. `null` until the account's first conversation.
        items:
          type: array
          items:
            $ref: '#/components/schemas/WorkspaceThreadRow'
    WorkspaceThreadRow:
      type: object
      properties:
        id:
          type: string
        workspaceId:
          type: string
        workspaceName:
          type: string
        title:
          type: string
        kind:
          type: string
        archived:
          type: boolean
        updatedAt:
          type: string
          format: date-time
        unread:
          type: boolean
        unreadCount:
          type: integer
        unreadMentionCount:
          type: integer
        manualUnread:
          type: boolean
        lastReadSeq:
          type: integer
        lastMessageSeq:
          type: integer
        waitingForMe:
          type: integer
          description: 'Runs waiting for this person: a question or an approval.'
        activeRunCount:
          type: integer
        directUserUIDs:
          type: array
          items:
            type: string
          description: 'Private conversations (`kind: "direct"`): the two participants.'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        An API key from your Devic console, sent as `Authorization: Bearer
        <key>`. An embedded front end sends a tenant-session token instead, so
        no API key reaches the browser, and an OAuth integration sends its
        access token. Missing, invalid or expired credentials get a `401`. See
        [Authentication](/api-reference/introduction#authentication).

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.