Skip to main content
The Corti Embedded Assistant API enables seamless integration of Corti Assistant into host applications, such as Electronic Health Record (EHR) systems, web-based clinical portals, or native applications using embedded WebViews. The implementation provides a robust, consistent, and secure interface for parent applications to control and interact with embedded Corti Assistant.
The details outlined below are for you to embed the Corti Assistant “AI scribe solution” natively within your application. To learn more about the full Corti API, please see more here

​
Quick Start Guides

Get started quickly with our platform-specific integration guides:

React Web App

Complete guide for React applications with the Web Component API
C#/.NET Desktop Guide Coming SoonA complete integration guide for WPF, WinForms, and .NET MAUI applications using WebView2 is coming in Q1 2026. In the meantime, the Web Component API works with any WebView-based application.

​
Overview

The Embedded Assistant API is a communication interface that allows your application to embed and control Corti Assistant within your own application interface. It provides programmatic control over authentication, session management, interaction creation, document generation, and more. The API enables two-way communication between your application and the embedded Corti Assistant, allowing you to:
  • Authenticate users and manage sessions
  • Create and manage clinical interactions
  • Configure the Assistant interface and appearance
  • Control recording functionality
  • Receive real-time events and updates
  • Access generated documents and transcripts

​
Requirements

Before getting started, ensure you have:
  • Created an OAuth Client for Corti Assistant: You’ll need to create a Corti Assistant specific client from the Developer Console.
  • Modern browser or WebView: For web applications, use a modern browser (Chrome, Firefox, Safari, or Edge). For native apps, use a modern WebView (WebView2, WKWebView, or Chromium-based WebView)
  • HTTPS: The embedded Assistant must be loaded over HTTPS (required for microphone access)
  • Microphone permissions: Your application must request and handle microphone permissions appropriately
  • OAuth2 client: You’ll need an OAuth2 client configured for user-based authentication

​
Available Regions

​
Integration Methods

The Embedded Assistant API offers three integration methods. For most use cases, we recommend the Web Component API for its simplicity and broad compatibility. For detailed comparison and guidance, see the Integration Method Comparison Guide. Works for all scenarios: iframe, WebView, same-origin, and cross-origin. Framework-agnostic with built-in React support and full TypeScript definitions. Web Component API Documentation | Full Examples

​
Alternative Methods

  • PostMessage API - Lower-level iframe communication (not recommended for new integrations)
  • Window API - Same-origin direct access for specific use cases

​
Documentation

​
Next Steps

  1. Follow a platform-specific guide to get started quickly
  2. Review the OAuth Authentication Guide to set up user authentication
  3. Choose your integration method based on your use case
  4. Consult the API Reference for all available methods and events
Please contact us for help or questions.