curl --request POST \
--url https://pria.praxislxp.com/api/user/uploads/files-with-issues \
--header 'Content-Type: application/json' \
--header 'x-access-token: <api-key>' \
--data '
{
"institution": "<string>",
"collection": "<string>"
}
'{
"success": true,
"files": [
{
"_id": "<string>",
"name": "<string>",
"score": 123,
"hasFix": true,
"collection_path": [
{
"_id": "<string>",
"name": "<string>",
"color": "<string>"
}
]
}
]
}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.
curl --request POST \
--url https://pria.praxislxp.com/api/user/uploads/files-with-issues \
--header 'Content-Type: application/json' \
--header 'x-access-token: <api-key>' \
--data '
{
"institution": "<string>",
"collection": "<string>"
}
'{
"success": true,
"files": [
{
"_id": "<string>",
"name": "<string>",
"score": 123,
"hasFix": true,
"collection_path": [
{
"_id": "<string>",
"name": "<string>",
"color": "<string>"
}
]
}
]
}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.
Authorizations
JWT token passed in x-access-token header
Body
Vault scope. Same enum as vault-health-summary.
personal, instance, account Optional institution _id, honored only on the instance vault for cross-instance admin views.
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.
Was this page helpful?