Dialt
Get API key

Migration guide

Converse to Dialt

Use the Dialt names for all new integrations. Compatibility names still work so existing applications can migrate without downtime.

Name mapping

LegacyCanonical Dialt nameCompatibility
ck_...dk_... for newly issued keysExisting keys remain valid.
CONVERSE_API_KEYDIALT_API_KEYEnvironment fallback remains temporary.
@trelis/converse@dialt/sdk 0.27.1Install the Dialt package for updates.
ConverseClientDialtClientLegacy construction warns once.
mode.kind: 'converse'mode.kind: 'dialt'Legacy input warns once and is normalized.
converse-sdkdialt-sdk 0.20.0The final bridge remains installable.
converse_sdkdialtLegacy imports emit a deprecation warning.
ConverseError, ConverseMode, ConverseSessionDialtError, DialtMode, DialtSessionLegacy access warns once.
https://converse.trelis.comhttps://dialt.comHTTP redirects permanently with method preservation.
wss://converse.trelis.com/wswss://dialt.com/wsThe legacy WebSocket remains proxied because WebSockets do not follow redirects.

Browser

npm remove @trelis/converse
npm install @dialt/sdk

import { DialtClient } from '@dialt/sdk';

const client = new DialtClient({
  url: 'wss://dialt.com/ws',
  mode: { kind: 'dialt' },
});

Use the canonical Browser SDK guide for new integrations. It covers secure scoped credentials, SDK and AudioWorklet loading, microphone lifecycle, and input selection.

Python

uv remove converse-sdk
uv add dialt-sdk

from dialt import DialtMode, DialtSession

Credentials and endpoints

DIALT_API_KEY=dk_your_key

Mint browser credentials with POST https://dialt.com/api/v1/session-keys. Do not rely on an HTTP redirect for credential creation. Keep persistent keys out of browser JavaScript.

Compatibility policy

The warning-bearing releases provide a migration window. Dialt will announce a specific removal version before deleting legacy aliases. Existing persistent keys are not invalidated by the SDK migration.