> ## 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.
# Unlink LTI context from user institution
> Removes the LTI context association from a user institution, allowing reassociation with a different Digital Twin. Validates that the user institution exists, belongs to the authenticated user, has an LTI context linked, belongs to an institution, and the institution record exists. Also removes the context ID from the parent institution's ltiContextIds array.
## OpenAPI
````yaml /mdx/api-reference/runtime/runtime-api.json put /api/user/unlinkContextId/{id}
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/unlinkContextId/{id}:
put:
tags:
- User Institutions
summary: Unlink LTI context from user institution
description: >
Removes the LTI context association from a user institution, allowing
reassociation with a different Digital Twin. Validates that the user
institution exists, belongs to the authenticated user, has an LTI
context linked, belongs to an institution, and the institution record
exists. Also removes the context ID from the parent institution's
ltiContextIds array.
parameters:
- in: path
name: id
required: true
schema:
type: string
description: The user institution ID to unlink (must be a valid ObjectId)
responses:
'200':
description: LTI context removed successfully
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: true
message:
type: string
example: LTI context removed.
'400':
description: >-
Bad request - invalid ObjectId, user institution not found, no LTI
context linked, institution missing on record, or generic error
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: false
error:
type: string
description: >-
One of: 'User Institution not found', 'No LTI context
linked to this digital twin', 'LTI context must be for an
institution', or 'Failed to find userInstitution'
message:
type: string
description: >-
'Invalid user institution Id' (for invalid ObjectId) or
'Failed to find userInstitution' (for catch-all errors)
'401':
description: >-
Unauthorized - user not found or the user institution does not
belong to the authenticated user
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: false
error:
type: string
description: >-
Either 'Authentication required' (message field) or 'This
membership is not your!' (error field)
'404':
description: >-
Not found - the parent institution record does not exist in the
database
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: false
error:
type: string
example: Not found
security:
- apiKeyAuth: []
components:
securitySchemes:
apiKeyAuth:
type: apiKey
in: header
name: x-access-token
description: JWT token passed in x-access-token header
````