> ## 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.
# Save a meeting transcript record to the owner's personal vault ("Save transcript to vault").
> For a `type:'meeting'` History row (the live-built, speaker-attributed
Zoom/Meet/Teams transcript — spec
`docs/specs/2026-08-25-meeting-transcript-history-record-SPEC-AND-PLAN.md`),
serializes the canonical transcript to markdown
(`routes/logic/meetingTranscript.formatMeetingTranscript` — byte-identical
to what the UI "Copy" action emits), writes it into the caller's
**personal** vault under a "Meeting Transcripts" collection, creates the
`upload` row (`text/markdown`, `is_private:false`, personal — no
institution) and enqueues normal RAG ingestion so the transcript becomes
searchable knowledge.
- **Owner only**: `History.user === req.user._id`; other rows answer 404
(no existence oracle). Admin entitlement does not unlock another user's
transcript into this vault.
- **Server-authored**: the request body carries no content; the server
serializes the record.
- **Idempotent**: `meeting.vaultUpload` is the key — a repeat returns the
existing upload (`200`, `existing:true`). A trashed/deleted upload lets
a fresh save through.
- The upload deliberately carries no `history` backlink, so ingestion
cost is filed as a standalone `type:'ingestion'` row and never
mutates the meeting record's `credits` (a mirror of
`meeting.billing.creditsBilled`).
## OpenAPI
````yaml /mdx/api-reference/runtime/runtime-api.json post /api/user/history/{id}/meeting-transcript/vault
openapi: 3.0.0
info:
title: Pria Runtime API
version: 2.0.70
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/history/{id}/meeting-transcript/vault:
post:
tags:
- User
summary: >-
Save a meeting transcript record to the owner's personal vault ("Save
transcript to vault").
description: >
For a `type:'meeting'` History row (the live-built, speaker-attributed
Zoom/Meet/Teams transcript — spec
`docs/specs/2026-08-25-meeting-transcript-history-record-SPEC-AND-PLAN.md`),
serializes the canonical transcript to markdown
(`routes/logic/meetingTranscript.formatMeetingTranscript` —
byte-identical
to what the UI "Copy" action emits), writes it into the caller's
**personal** vault under a "Meeting Transcripts" collection, creates the
`upload` row (`text/markdown`, `is_private:false`, personal — no
institution) and enqueues normal RAG ingestion so the transcript becomes
searchable knowledge.
- **Owner only**: `History.user === req.user._id`; other rows answer 404
(no existence oracle). Admin entitlement does not unlock another user's
transcript into this vault.
- **Server-authored**: the request body carries no content; the server
serializes the record.
- **Idempotent**: `meeting.vaultUpload` is the key — a repeat returns
the
existing upload (`200`, `existing:true`). A trashed/deleted upload lets
a fresh save through.
- The upload deliberately carries no `history` backlink, so ingestion
cost is filed as a standalone `type:'ingestion'` row and never
mutates the meeting record's `credits` (a mirror of
`meeting.billing.creditsBilled`).
parameters:
- name: id
in: path
required: true
description: The meeting History row's `_id`.
schema:
type: string
pattern: ^[a-f0-9]{24}$
responses:
'200':
description: >-
Already saved — the existing vault upload is returned
(`existing:true`).
'201':
description: Transcript written and queued for indexing.
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: true
data:
type: object
properties:
uploadId:
type: string
url:
type: string
description: The vault file URL.
filename:
type: string
description: Sanitized on-disk name.
originalname:
type: string
example: Meeting transcript - Weekly sync - 2026-09-01.md
collection:
type: string
nullable: true
collectionName:
type: string
example: Meeting Transcripts
status:
type: string
example: inactive
existing:
type: boolean
example: false
queued:
type: boolean
description: >-
false when the ingestion queue refused the job (upload
annotated for the sweeper).
'400':
description: >-
Invalid id, not a meeting record, or the record has no transcript
content.
'401':
description: Authentication required.
'404':
description: History not found (or not owned by the caller).
'500':
description: Save failed (generic; no raw fs/db error is leaked).
security:
- apiKeyAuth: []
components:
securitySchemes:
apiKeyAuth:
type: apiKey
in: header
name: x-access-token
description: JWT token passed in x-access-token header
````