> ## 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.
# List every file with a vault-health issue
> Companion to `/api/user/uploads/vault-health-summary` — returns the full *list* of problematic files in scope (vault, or vault + collection subtree), classified into one of eight issue categories. Both endpoints share the same `$match` predicates so the list and the pill counts on the Vault Health panel always agree.
Issue classification mirrors the client's legacy `filesWithIssues` priority order (first match wins):
`missing_terminal > missing_file > unindexed > stale_base_url > unoptimized > error > never_used > stale`.
Returned uncapped — problem inventory is naturally bounded by the vault's issue count, not browse pagination. Files-with-issues counts in the summary endpoint are also uncapped, so the list always matches.
## OpenAPI
````yaml /mdx/api-reference/runtime/runtime-api.json post /api/user/uploads/files-with-issues
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.
They use many standard HTTP features, including methods (POST,
GET, PUT, DELETE) and error response codes.
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/uploads/files-with-issues:
post:
tags:
- IP Vault
summary: List every file with a vault-health issue
description: >
Companion to `/api/user/uploads/vault-health-summary` — returns the full
*list* of problematic files in scope (vault, or vault + collection
subtree), classified into one of eight issue categories. Both endpoints
share the same `$match` predicates so the list and the pill counts on
the Vault Health panel always agree.
Issue classification mirrors the client's legacy `filesWithIssues`
priority order (first match wins):
`missing_terminal > missing_file > unindexed > stale_base_url >
unoptimized > error > never_used > stale`.
Returned uncapped — problem inventory is naturally bounded by the
vault's issue count, not browse pagination. Files-with-issues counts in
the summary endpoint are also uncapped, so the list always matches.
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- vault
properties:
vault:
type: string
enum:
- personal
- instance
- account
description: Vault scope. Same enum as vault-health-summary.
institution:
type: string
description: >-
Optional institution _id, honored only on the `instance`
vault for cross-instance admin views.
collection:
type: string
description: >
Optional ObjectId. When set, narrows the listing to files
inside that collection AND its descendants (walks
`collection.parent` to bounded depth-10). When omitted, the
listing covers the entire vault. The UI's "List across all
collections in this vault" checkbox omits this field;
unchecked + active collection passes the active collection
id so the panel scopes to what the user is browsing.
responses:
'200':
description: Files with issues
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: true
files:
type: array
items:
type: object
properties:
_id:
type: string
name:
type: string
description: Upload's originalname
issue:
type: string
enum:
- missing_terminal
- missing_file
- unindexed
- stale_base_url
- unoptimized
- error
- never_used
- stale
score:
type: integer
description: >-
Only present for issue=unoptimized — the
vaultHealthScore (0-100 percentage of
code/markup/structured content).
hasFix:
type: boolean
description: >-
Only present for issue=stale_base_url. Currently
always true on this endpoint.
collection_path:
type: array
description: >-
Breadcrumb from root → leaf of the file's containing
collection. Omitted when the file lives at the vault
root.
items:
type: object
properties:
_id:
type: string
name:
type: string
color:
type: string
nullable: true
'400':
description: Bad request — missing/invalid vault, or invalid collection id
'401':
description: Unauthorized
security:
- apiKeyAuth: []
components:
securitySchemes:
apiKeyAuth:
type: apiKey
in: header
name: x-access-token
description: JWT token passed in x-access-token header
````