> ## 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.
# Rename a conversation or favorite
> Two modes of operation: (1) Rename a conversation by providing course_id and course_name - updates all history records in that conversation within the resolved institution scope. (2) Rename a favorite by providing id and favorite_name - updates a single record. If favorite_name is falsy, the field is removed ($unset). Conversation renames support institution scoping (ObjectId / explicit null = personal / omitted = user.institution fallback); allInstitutions:true is rejected with 400.
## OpenAPI
````yaml /mdx/api-reference/runtime/runtime-api.json post /api/user/renameHistory
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/renameHistory:
post:
tags:
- History
summary: Rename a conversation or favorite
description: >-
Two modes of operation: (1) Rename a conversation by providing course_id
and course_name - updates all history records in that conversation
within the resolved institution scope. (2) Rename a favorite by
providing id and favorite_name - updates a single record. If
favorite_name is falsy, the field is removed ($unset). Conversation
renames support institution scoping (ObjectId / explicit null = personal
/ omitted = user.institution fallback); allInstitutions:true is rejected
with 400.
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/RenameHistoryRequest'
examples:
renameCourse:
summary: Rename a conversation
value:
course_id: 1750532703472
course_name: My Renamed Conversation
renameFavorite:
summary: Rename a favorite
value:
id: 688b024f7db6fe6e921399e3
favorite_name: Deployment Guide
clearFavoriteName:
summary: Remove a favorite name
value:
id: 688b024f7db6fe6e921399e3
favorite_name: ''
responses:
'200':
description: Record(s) successfully renamed
content:
application/json:
schema:
$ref: '#/components/schemas/RenameHistoryResponse'
examples:
courseRenamed:
summary: Conversation renamed
value:
success: true
message: Conversation renamed!
favoriteRenamed:
summary: Favorite renamed
value:
success: true
message: Favorite renamed!
'400':
description: >-
Bad request - invalid course_id type, malformed institution
ObjectId, missing parameters, or allInstitutions:true was supplied.
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: false
message:
type: string
example: >-
Invalid parameters. You must either rename a conversation
or rename a favorite.
error:
type: object
'401':
description: Unauthorized - user not found or invalid token
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: false
message:
type: string
example: Authentication Required!
'403':
description: >-
Forbidden - the supplied institution ObjectId is not an active
UserInstitution membership for this user.
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: false
message:
type: string
example: You are not a member of this institution
security:
- apiKeyAuth: []
components:
schemas:
RenameHistoryRequest:
type: object
description: >-
Two mutually exclusive modes. Either rename a conversation (course_id +
course_name) or rename a favorite (id + favorite_name). Conversation
renames support institution scoping.
properties:
course_id:
type: number
description: >-
Course identifier for renaming a conversation. Must be paired with
course_name. course_id=0 sweeps the unassigned bucket.
example: 1750532703472
course_name:
type: string
description: New name for the conversation. Used with course_id.
example: My Renamed Conversation
institution:
type: string
nullable: true
description: >-
Institution scope (course_id mode only). Three-state: (1) valid
ObjectId scopes to that twin (membership-checked — 403 if not
active), (2) explicit null/empty scopes to personal/null history,
(3) field omitted falls back to user.institution. Malformed ObjectId
returns 400.
id:
type: string
description: >-
ObjectId of the favorite record to rename. Must be paired with
favorite_name. Single-record operations are not institution-scoped
(_id is globally unique).
example: 688b024f7db6fe6e921399e3
favorite_name:
type: string
description: >-
New name for the favorite. If falsy (empty string or null), the
favorite_name field is removed via $unset.
example: Deployment Guide
RenameHistoryResponse:
type: object
properties:
success:
type: boolean
example: true
message:
type: string
description: >-
Either 'Conversation renamed!' or 'Favorite renamed!' depending on
the mode used
example: Conversation renamed!
securitySchemes:
apiKeyAuth:
type: apiKey
in: header
name: x-access-token
description: JWT token passed in x-access-token header
````