Use this page to track announced Embedded API changes that have a scheduled end-of-support date and may require action in existing Corti Assistant integrations.Documentation Index
Fetch the complete documentation index at: https://docs.corti.ai/llms.txt
Use this file to discover all available pages before exploring further.
How to use this page
- This page lists only deprecations with a dated migration window and a clear customer action.
- Newly announced but fully backward-compatible improvements stay in the Corti Assistant release notes until there is a scheduled removal date to track here.
- Each entry includes what is changing, when it was announced, the expected shutdown date, and where to migrate next.
Deprecated Embedded API functionality remains functional for 6 months after
the deprecation is announced in release notes or on this page.When it is technically possible, deprecations also include at least 2 months
of warnings on use before shutdown.
Subscribe to updates
- Use the RSS feed for this page if you want embedded-specific deprecation updates only.
- Follow the Corti Assistant release notes for broader Embedded API and application changes.
Highest-priority migration
Legacy embedded events (due August 20, 2026)
This is the next Embedded API change with a scheduled shutdown date.| Item | Details |
|---|---|
| Status | Migrate now |
| What is changing | The legacy embedded event system is being removed in favor of the current embedded event system. |
| Announced | 2026-02-20 in the Corti Assistant release notes (v12.10.0) |
| Expected shutdown date | 2026-08-20 |
| Required action | Update event subscriptions to the current event names and payloads before the shutdown date. |
| Migration path | Use the Events Migration Guide for migration recommendations, then update subscriptions using the current event reference pages. |
Other scheduled changes
Embedded configuration API split (due November 29, 2026)
configureApp() and setInteractionOptions() were added to the Embedded API,
splitting app-level configuration from interaction-level options such as mode,
spoken language, template defaults, and document actions.
| Item | Details |
|---|---|
| Status | Plan migration |
| What is changing | The existing configure() and configureSession() methods are deprecated and are being replaced by configureApp() and setInteractionOptions(). |
| Before | configure() and configureSession() handled a mix of app-level configuration and interaction defaults. |
| Going forward | Use configureApp() for app-level settings. Use setInteractionOptions() for interaction-level options such as mode, spoken language, template defaults, and document actions. |
| Announced | 2026-05-29 in the Corti Assistant release notes (v12.18.0) |
| Expected shutdown date | 2026-11-29 |
| Required action | Move app-level settings to configureApp() and move interaction-level options to setInteractionOptions(). |
| Migration path | Use the Config Migration Guide and Configuration Scenarios. |
A deprecation means you should plan a migration. It does not mean you need to
stop using the existing API immediately.
Related pages
Corti Assistant Release Notes
Follow Embedded API announcements and broader Assistant changes.
Config Migration Guide
Move existing
configure() and configureSession() calls to the new
configuration structure.Configuration Scenarios
See scenario-based examples for app-level settings and interaction options.