> ## 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 one presentation video and its versions
> Your presentation and its versions (newest first, without their content). An administrator of the presentation's Digital Twin may read it for support; every such read is recorded.
## OpenAPI
````yaml /mdx/api-reference/runtime/runtime-api.json get /api/user/presentations/{id}
openapi: 3.0.0
info:
title: Pria Runtime API
version: 2.0.236
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.
A
session that a course page (Canvas) opened for an administrator — or that a
Digital Twin's sign-in provider opened for one of its people — starts with
user rights in that twin only: until the person confirms it's them with a
code (POST /api/user/launch-scope/challenge, then /api/auth/mfa-resend and
/api/auth/mfa-verify), every route outside that twin's day-to-day work
answers 403 with code LAUNCH_SCOPE_STEP_UP and the twin's id.
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/presentations/{id}:
get:
tags:
- Presentations
summary: Get one presentation video and its versions
description: >
Your presentation and its versions (newest first, without their
content). An administrator of the presentation's Digital Twin may read
it for support; every such read is recorded.
parameters:
- in: path
name: id
required: true
schema:
type: string
responses:
'200':
description: The presentation
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: true
access:
type: string
enum:
- owner
- admin
presentation:
$ref: '#/components/schemas/PresentationSummary'
revisions:
type: array
description: >-
One row per version (a unit of work: one build, fix rounds
included, or one edit), newest first; each row is the
version's newest revision
items:
type: object
properties:
number:
type: integer
example: 22
description: >-
The version's newest revision (read it with
/revisions/{n})
version:
type: integer
example: 1
description: The version the owner sees (Version 1, 2, …)
parent:
type: integer
nullable: true
example: 21
authorRole:
type: string
example: designer
reason:
type: string
rendererVersion:
type: string
example: 1.0.0
createdAt:
type: string
format: date-time
narration:
type: object
properties:
status:
type: string
enum:
- none
- pending
- running
- ready
- failed
presenter:
type: object
nullable: true
description: >-
The Digital Twin's face job for this version (null
when it has none) — the versions list's "Recording
face…" note
properties:
status:
type: string
enum:
- queued
- launching
- recording
- aligning
- ready
- failed
- skipped
length:
type: object
description: >-
Only for a video longer than 1 minute (absent for a
1-minute or older video): its length and the waits that go
with it — the same object as the version read's `length`,
here so a first build is known before any version is saved
properties:
seconds:
type: integer
example: 180
waits:
type: object
properties:
build:
type: array
nullable: true
items:
type: integer
example:
- 10
- 20
description: >-
Minutes a first build usually takes (null: a few
minutes)
faceS:
type: integer
example: 540
description: >-
Seconds the Digital Twin's face usually takes to
record
exportS:
type: integer
nullable: true
example: 180
description: >-
Seconds an export usually takes (null: no estimate
shown)
pollMinutes:
type: object
properties:
build:
type: integer
example: 30
description: How long the app keeps checking a build
face:
type: integer
example: 25
description: How long the app keeps checking the face
'401':
description: Not signed in
'404':
description: >-
No such presentation of yours in your current Digital Twin, or the
feature is off
security:
- apiKeyAuth: []
components:
schemas:
PresentationSummary:
type: object
properties:
_id:
type: string
title:
type: string
example: Q3 in 60 seconds
status:
type: string
enum:
- building
- previewable
- failed
failureCode:
type: string
example: BUILD_STALE
narrationCapMinutes:
type: integer
example: 30
description: >-
Only when failureCode is NARRATION_DAILY_CAP: today's voice-over
limit in minutes (the server's daily narration cap)
headRevision:
type: integer
example: 22
description: The head revision number; 0 = no version yet
headVersion:
type: integer
example: 1
description: The head's version
estimateCredits:
type: integer
example: 15
description: >-
About how many credits the video was expected to cost when it was
started: the high end of the range (absent on older videos)
estimateLow:
type: integer
example: 10
description: The low end of that range (absent on videos started before ranges)
stoppedAt:
type: string
format: date-time
description: When you stopped the video (absent unless stopped)
stopReason:
type: string
enum:
- STOP
- CANCEL
description: >-
STOP = stopped during the answer that made it; CANCEL = Stop video
afterwards
stopAvailable:
type: boolean
description: >-
Your own video only: it can still be stopped (it is being made, or
its presenter recording has not started), and its current version is
not stopped yet
headStopped:
type: boolean
description: >-
Your own video only: its current version was stopped (a later change
of a stopped video can be stopped again)
buildTurnKey:
type: string
description: >-
Your own video only: the chat answer that is making (or last made)
this video — send it as turn_id with a Stop
costIncluded:
type: boolean
description: >-
Your own video only, present (true) when your plan includes videos
(you are not charged for them); then there is no estimateCredits or
estimateLow
createdAt:
type: string
format: date-time
updatedAt:
type: string
format: date-time
securitySchemes:
apiKeyAuth:
type: apiKey
in: header
name: x-access-token
description: JWT token passed in x-access-token header
````
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.