> ## 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.
# Upload one or more audio segments for transcription and vault ingestion
> Accepts 1..20 audio segments (audio/webm, audio/ogg, audio/mp4, audio/mpeg, audio/wav).
Each segment is capped at 50 MB. When `combine=true` and all segments share a single
mimetype, the server concatenates them losslessly via ffmpeg before ingestion.
Returns 202 immediately; transcription runs asynchronously through the existing
ingestion queue and produces a transcript-derived file_title.
## OpenAPI
````yaml /mdx/api-reference/runtime/runtime-api.json post /api/user/audio-notes
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/audio-notes:
post:
tags:
- Audio Notes
summary: Upload one or more audio segments for transcription and vault ingestion
description: >
Accepts 1..20 audio segments (audio/webm, audio/ogg, audio/mp4,
audio/mpeg, audio/wav).
Each segment is capped at 50 MB. When `combine=true` and all segments
share a single
mimetype, the server concatenates them losslessly via ffmpeg before
ingestion.
Returns 202 immediately; transcription runs asynchronously through the
existing
ingestion queue and produces a transcript-derived file_title.
requestBody:
required: true
content:
multipart/form-data:
schema:
type: object
required:
- files
properties:
files:
type: array
items:
type: string
format: binary
combine:
type: string
enum:
- 'true'
- 'false'
description: >-
When true and all segments share a single mimetype, the
server losslessly concatenates them via ffmpeg into a single
upload before ingestion. Falls back to per-segment uploads
on mismatch or concat failure.
segment_names:
type: array
items:
type: string
description: >-
Optional names parallel to files[]; ignored when
combine=true
selectedCourse:
type: string
description: >
Optional JSON-stringified course context (`{ course_id,
course_name, assistant: { _id } }`) — applied to the History
row that runFinalize updates as ingestion completes. Same
shape as `POST /user/files`.
selectedAssistant:
type: string
description: >-
Optional active-assistant ObjectId — used as the History
row's `assistant` field when no `selectedCourse.assistant`
is provided.
responses:
'202':
description: Accepted — uploads queued for background ingestion
content:
application/json:
schema:
type: object
properties:
acknowledged:
type: boolean
uploads:
type: array
items:
type: object
properties:
id:
type: string
originalname:
type: string
status:
type: string
'400':
description: Invalid input (no files, file too large, etc.)
'403':
description: Personal upload disabled by institution
security:
- bearerAuth: []
components:
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
description: JWT token passed in authorization header
````