> ## 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.

# A teacher disconnects a disabled Digital Twin from its Canvas course

> The ONE public way a held Canvas course becomes free again (design 2026-09-28 D6): a
teacher — proven only by a course ticket, at the `UNLINK_TRUST` level (an in-process LTI
1.3 launch by default) — disconnects the DISABLED Digital Twin that holds the course, so
it can be connected to a different twin. A twin merely blocked by its account is never
touched (that block is the twin's to walk back, not the course's), and a course a USABLE
twin holds is refused. Rate-limited with the signup-grade limiter because it writes.




## OpenAPI

````yaml /mdx/api-reference/admin/admin-api.json post /api/auth/sdk-unlink-course
openapi: 3.0.0
info:
  title: Pria Admin API
  version: 2.0.183
  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.
    <br/>  <br/>They use many standard HTTP features, including methods (POST,
    GET, PUT, DELETE) and error response codes.  <br/> <br/>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: Admin Memory
    description: Admin inspection and editing of user/instance memory parameters.
  - name: Admin Usage Limits
    description: Per-user usage-vs-cap reporting and account-wide at-limit counts.
paths:
  /api/auth/sdk-unlink-course:
    post:
      tags:
        - SDK Launch
      summary: A teacher disconnects a disabled Digital Twin from its Canvas course
      description: >
        The ONE public way a held Canvas course becomes free again (design
        2026-09-28 D6): a

        teacher — proven only by a course ticket, at the `UNLINK_TRUST` level
        (an in-process LTI

        1.3 launch by default) — disconnects the DISABLED Digital Twin that
        holds the course, so

        it can be connected to a different twin. A twin merely blocked by its
        account is never

        touched (that block is the twin's to walk back, not the course's), and a
        course a USABLE

        twin holds is refused. Rate-limited with the signup-grade limiter
        because it writes.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SdkUnlinkCourseRequest'
      responses:
        '200':
          description: >-
            Disconnected (or already free) — this is a success even when
            `unlinked` is 0.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SdkUnlinkCourseResponse'
        '400':
          description: '"Missing verification parameters" — no ticket was sent.'
        '403':
          description: >-
            "Ask a Pria administrator to disconnect this course." — the ticket's
            holder may not unlink under the current UNLINK_TRUST.
        '409':
          description: >-
            "This course is connected to an active Digital Twin." (a USABLE twin
            holds it), or "This course is connected to a Digital Twin whose
            account is disabled." (every holder is blocked by its account rather
            than disabled — nothing to disconnect from here).
        '410':
          description: >-
            The ticket is expired or invalid: `{ success: false, code:
            "COURSE_TICKET_EXPIRED" | "COURSE_TICKET_INVALID", message: "This
            page has expired" }`.
        '500':
          description: '"Could not disconnect the course"'
components:
  schemas:
    SdkUnlinkCourseRequest:
      type: object
      required:
        - ticket
      properties:
        ticket:
          type: string
          description: >-
            A course ticket minted for a teacher by
            `getInstitutionsForContextid` or `sdk-hide`. Identity and course
            come from the ticket alone; no other body field is honoured.
    SdkUnlinkCourseResponse:
      type: object
      properties:
        success:
          type: boolean
          example: true
        unlinked:
          type: integer
          description: >-
            How many disabled twins the course was pulled off (0 when someone
            else already did it — still a success).
          example: 1
        blocked:
          type: integer
          description: >-
            How many holders were left untouched because they are merely blocked
            by their account, not disabled.
          example: 0

````