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

# Get all file and collection IDs for bulk select-all

> Returns all file IDs and collection IDs matching the current scope (vault
root or inside a collection), honoring the active filters from the UI
(file-name search, status filter). When any filter is active, collections
are NOT returned — selecting a whole collection would pull in non-matching
files inside it, which is unsafe for bulk delete.




## OpenAPI

````yaml /mdx/api-reference/runtime/runtime-api.json post /api/user/collections/select-all-ids
openapi: 3.0.0
info:
  title: Pria Runtime API
  version: 2.0.1
  description: >-
    Pria API Documentation Praxis's developer platform is a core part of our
    mission to empower organizations to grow better. Our APIs are designed to
    enable teams of any shape or size to build robust integrations that help
    them customize and get the most value out of Pria. All Pria APIs are built
    using REST conventions and designed to have a predictable URL structure.
    <br/>  <br/>They use many standard HTTP features, including methods (POST,
    GET, PUT, DELETE) and error response codes.  <br/> <br/>All API calls are
    made under https://hiimpria.ai/api and all responses return standard JSON.
    In these docs, you'll find lists of all available endpoints for a given API,
    along with interactive code blocks for building requests. For walkthroughs
    of basic usage for these APIs, check out the API guides.
servers:
  - url: https://pria.praxislxp.com
    description: Pria API Server
security: []
tags:
  - name: Authentication
    description: User authentication, registration, and password management (/api/auth)
  - name: OAuth
    description: OAuth authentication providers - Google, GitHub, SSO (/api/auth/oauth)
  - name: User
    description: User profile management and account operations (/api/user)
  - name: User Institutions
    description: User institution memberships and switching (/api/user/institution)
  - name: User Tools
    description: Available tools for authenticated users (/api/user/tools)
  - name: Institutions
    description: Institution settings and configuration (/api/user/institution)
  - name: Conversation
    description: AI conversation and Q&A endpoints (/api/ai)
  - name: Realtime
    description: Real-time voice AI and WebRTC sessions (/api/ai/rt)
  - name: Assistant
    description: AI assistant configuration and management (/api/user/assistant)
  - name: History
    description: Conversation history and favorites (/api/user/history)
  - name: RAG
    description: >-
      Document upload, embedding, and retrieval-augmented generation
      (/api/user/files, /api/user/rag)
  - name: Setting
    description: Instance variables and settings management (/api/user/setting)
  - name: Branding
    description: Digital twin branding and customization (/api/agent/branding)
  - name: Agent
    description: Agent engagement and session management (/api/agent)
  - name: SDK Launch
    description: >-
      SDK launch token signing and verification for secure iframe embedding
      (/api/auth/sdk-sign, /api/auth/sdk-verify)
  - name: Testing
    description: Health checks, diagnostics, and test endpoints (/api/test)
  - name: Admin Accounts
    description: Account management for super admins (/api/admin/account)
  - name: Admin Institutions
    description: Institution management for admins (/api/admin/institution)
  - name: Admin Users
    description: User management for admins (/api/admin/user)
  - name: Admin Entitlements
    description: >-
      User-institution relationships and permissions
      (/api/admin/userInstitution)
  - name: Admin Sessions
    description: Session management for admins (/api/admin/session)
  - name: Admin Histories
    description: Conversation history management and analytics (/api/admin/history)
  - name: Admin Assistants
    description: AI assistant management for admins (/api/admin/assistant)
  - name: Admin Questions
    description: Institution question and prompt management (/api/admin/question)
  - name: Admin Tools
    description: Tool configuration management (/api/admin/tool)
  - name: Admin AI Models
    description: AI model configuration (/api/admin/aimodel)
  - name: Admin MCP Servers
    description: Model Context Protocol server management (/api/admin/mcpserver)
  - name: Admin Feedbacks
    description: User feedback management (/api/admin/feedback)
  - name: Admin Uploads
    description: Upload management (/api/admin/upload)
  - name: Admin Charts
    description: Analytics and visualization chart management (/api/admin/chart)
  - name: Audio Notes
    description: Capture and ingest spoken notes into the personal vault
  - name: Memory
    description: User-facing memory parameters (personal + shared instance memory).
  - name: My Data
    description: >-
      GDPR controls — personal-scope counts, async ZIP-by-email export, and
      scoped soft-delete. Every endpoint pins `user = req.user._id` AND
      `institution: null`; institution-scoped data is governed by the
      institution's own retention policy and never reached from here.
  - name: Questions
    description: >-
      User-facing read of the onboarding question bank used by the "create a
      digital twin" wizard.
  - name: Transcription
    description: >-
      One-shot speech-to-text for in-place dictation. Audio blob in, transcript
      out — no Upload / History / RAG embeddings are persisted. Use
      `/audio-notes` for anything durable.
paths:
  /api/user/collections/select-all-ids:
    post:
      tags:
        - Collections
      summary: Get all file and collection IDs for bulk select-all
      description: >
        Returns all file IDs and collection IDs matching the current scope
        (vault

        root or inside a collection), honoring the active filters from the UI

        (file-name search, status filter). When any filter is active,
        collections

        are NOT returned — selecting a whole collection would pull in
        non-matching

        files inside it, which is unsafe for bulk delete.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                vault:
                  type: string
                  enum:
                    - personal
                    - instance
                    - account
                  description: Vault scope (required at root level)
                parent:
                  type: string
                  nullable: true
                  description: Collection ID to scope within (null for vault root)
                institution:
                  type: string
                  description: Override institution ID
                fileNameSearch:
                  type: string
                  description: Case-insensitive substring filter on file originalname
                status:
                  type: string
                  description: >-
                    Filter files by status. 'excluded' means $nin [selected,
                    deleted].
                  enum:
                    - active
                    - inactive
                    - selected
                    - error
                    - deleted
                    - excluded
      responses:
        '200':
          description: Selection IDs and names
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  files:
                    type: array
                    description: Files that will be selected (id + name preview)
                    items:
                      type: object
                      properties:
                        _id:
                          type: string
                        originalname:
                          type: string
                  collections:
                    type: array
                    description: >-
                      Collections that will be selected (empty when a filter is
                      active)
                    items:
                      type: object
                      properties:
                        _id:
                          type: string
                        name:
                          type: string
                        fileCount:
                          type: integer
                  fileIds:
                    type: array
                    description: Legacy bare-id list (mirrors files[]._id)
                    items:
                      type: string
                  collectionIds:
                    type: array
                    description: Legacy bare-id list (mirrors collections[]._id)
                    items:
                      type: string
                  totalFiles:
                    type: integer
                  filtered:
                    type: boolean
                    description: >-
                      True when a fileNameSearch or status filter scoped the
                      result
      security:
        - bearerAuth: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: JWT token passed in authorization header

````