> ## 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 your logo for this video > The owner's own logo, as the raw request body (any content type: the bytes decide the format). PNG, JPEG or WebP (an animated image gives its first frame); SVG only where the operator has switched it on (otherwise 415 LOGO_FORMAT "Please upload a PNG of your logo."). At most 5 MB and 4096 px a side. The logo is trimmed to its ink, fitted inside 1920 × 512 and stored as a PNG with its transparency and no metadata. It must be at least 48 px on its short side and at most 12 times as wide as it is tall (or 2 times as tall as it is wide). An SVG is refused if it holds anything beyond plain shapes, paths and gradients (scripts, styles, text, images, links, external references, document type declarations). `onDark` says whether the logo is drawn for dark backgrounds; a dark logo of one colour also gets an automatic white version (`variant`, `auto: true`) for dark looks. Nothing about the video changes until the brand is saved. Owner only; 10 uploads per minute. Not available while brand colours are switched off (404). ## OpenAPI ````yaml /mdx/api-reference/runtime/runtime-api.json post /api/user/presentations/{id}/brand/logo 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}/brand/logo: post: tags: - Presentations summary: Upload your logo for this video description: > The owner's own logo, as the raw request body (any content type: the bytes decide the format). PNG, JPEG or WebP (an animated image gives its first frame); SVG only where the operator has switched it on (otherwise 415 LOGO_FORMAT "Please upload a PNG of your logo."). At most 5 MB and 4096 px a side. The logo is trimmed to its ink, fitted inside 1920 × 512 and stored as a PNG with its transparency and no metadata. It must be at least 48 px on its short side and at most 12 times as wide as it is tall (or 2 times as tall as it is wide). An SVG is refused if it holds anything beyond plain shapes, paths and gradients (scripts, styles, text, images, links, external references, document type declarations). `onDark` says whether the logo is drawn for dark backgrounds; a dark logo of one colour also gets an automatic white version (`variant`, `auto: true`) for dark looks. Nothing about the video changes until the brand is saved. Owner only; 10 uploads per minute. Not available while brand colours are switched off (404). parameters: - in: path name: id required: true schema: type: string requestBody: required: true content: application/octet-stream: schema: type: string format: binary image/png: schema: type: string format: binary responses: '201': description: Stored (the same bytes again answer the same logo) content: application/json: schema: type: object properties: success: type: boolean example: true logo: type: object properties: asset: type: string example: asset:0123456789abcdef01234567 w: type: integer example: 880 h: type: integer example: 240 onDark: type: boolean description: 'true: the logo is drawn for dark backgrounds' variant: type: object description: >- Only for a dark one-colour logo with a transparent background: the automatic white version (used on dark looks when the brand is saved) properties: asset: type: string w: type: integer h: type: integer onDark: type: boolean example: true auto: type: boolean example: true variantRefused: type: string example: LOGO_CAP description: >- Present only when the white version could not be stored (the logo itself was) '401': description: Not signed in '404': description: Not yours, being deleted, or the feature (or brand colours) is off '409': description: >- LOGO_CAP { message } (this video has already used 4 logos, its earlier versions included: upload one of them again or apply a saved brand that uses one) '413': description: >- LOGO_TOO_LARGE (over 5 MB, over 4096 px a side, or an SVG over 1 MB or beyond its size limits) '415': description: >- LOGO_FORMAT { message } — not a PNG, JPEG or WebP (or an SVG that is switched off or would need cleaning) '422': description: >- LOGO_TOO_SMALL, LOGO_ASPECT, LOGO_UNREADABLE (empty, fully transparent, broken, or an SVG that did not render in time) '429': description: RATE_LIMITED (10 uploads/min) '503': description: LOGOS_UNAVAILABLE security: - apiKeyAuth: [] components: 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.