Legacy Pulse STT WebSocket reference removed from docs
The legacy WebSocket reference at wss://api.smallest.ai/waves/v1/lightning/get_text has been removed from the docs. Pulse STT (wss://api.smallest.ai/waves/v1/pulse/get_text) is the supported real-time STT surface; the legacy endpoint was already unlinked from the v4 API reference navigation and was only kept for historical reference.
Files removed:
- The legacy WebSocket API reference page (and its
versions/v4.0.0mirror). - The legacy AsyncAPI spec and its overrides under
fern/apis/waves/asyncapi/. - The corresponding generator entries in
fern/apis/waves/generators.ymlandfern/apis/unified/generators.yml. - The orphan-page allow-list entry in
scripts/.nav-ignore.
If your code still calls wss://api.smallest.ai/waves/v1/lightning/get_text, migrate to Pulse STT — the request shape is similar; see the Pulse STT quickstart and the Pulse WebSocket reference.
Pulse STT — multi-indic and multi-asian clarified as pre-recorded HTTP only (correction)
Pulse STT — multi-indic and multi-asian clarified as pre-recorded HTTP only (correction)
The multi-indic and multi-asian regional auto-detection scopes announced earlier today apply only to the Pulse STT pre-recorded HTTP endpoint (POST /waves/v1/pulse/get_text). They are not supported on the WebSocket streaming endpoint (wss://api.smallest.ai/waves/v1/pulse/get_text).
Specs and reference docs corrected accordingly:
fern/apis/waves/asyncapi/pulse-stt-ws.yaml—multi-indic/multi-asianremoved from the WebSocketlanguageenum.fern/apis/waves/asyncapi/pulse-stt-ws-overrides.yml— same.fern/apis/waves-v4/overrides/pulse-stt-ws-overrides.yml— same.fern/products/waves/pages/v4.0.0/api-references/pulse-stt-ws.mdx(+ versions mirror) — WebSocket reference table cell trimmed tomulti-eu/multionly.fern/products/waves/pages/v4.0.0/speech-to-text/pre-recorded/quickstart.mdx(+ versions mirror) — language Note now lists all four scopes (multi-eu,multi-indic,multi-asian,multi).
The pre-recorded OpenAPI spec (fern/apis/waves/openapi/pulse-stt-openapi.yaml) and the rendered API reference page (pulse-stt.mdx) continue to advertise all four scopes — that surface is unchanged.
The Pulse STT WebSocket probe (scripts/probes/pulse_stt.py) was also stripped of the two invalid test cases that were probing the WS endpoint with these scopes; the probe baseline (scripts/probes/baseline-pulse-stt.json) was regenerated.
If your code already passes language=multi-indic or language=multi-asian to the pre-recorded HTTP endpoint, no action needed — that path is correct. If you wired either scope into a WebSocket streaming call, switch back to multi-eu or multi until streaming-side coverage ships.
Pulse STT pre-recorded — multi-indic and multi-asian regional auto-detection modes
Pulse STT pre-recorded — multi-indic and multi-asian regional auto-detection modes
The language parameter on the Pulse STT pre-recorded HTTP endpoint now accepts two new regional auto-detection scopes alongside the existing multi-eu and multi:
multi-indic— auto-detects across the Indic set:en,hi,mr,pa,gu,or,ka,ta,te,ml,bn. Use for Indian-language audio with optional English code-switching.multi-asian— auto-detects across the East Asian set:en,ja,ko,zh,yue. Use for Japanese / Korean / Mandarin / Cantonese audio with optional English code-switching.
The existing scopes are unchanged:
multi-eu(default) —de,en,fr,it,nl,pt,ru,es.multi— full multilingual auto-detection across all supported languages.
Pick the narrowest scope that matches your audio for the best accuracy. Omitting language still routes to multi-eu and can mis-detect on non-European audio (e.g., returning Russian for English input).
The new multi-indic and multi-asian scopes are only available on the pre-recorded HTTP endpoint for now. The realtime WebSocket streaming endpoint continues to support only multi-eu and multi for auto-detection until streaming-side coverage ships.
Specs updated:
- OpenAPI (pre-recorded):
fern/apis/waves/openapi/pulse-stt-openapi.yaml
