AsyncAPI channel · Inworld AI
· Inworld AI Runtime WebSocket APIs
/stt/v1/transcribe:streamBidirectional
Bidirectional WebSocket endpoint for streaming speech-to-text
transcription. The first client message must be a TranscribeConfig
followed by AudioChunk messages and (optionally) EndTurn / CloseStream
control messages.
Provider:Inworld AIAsyncAPI: v2.6.0Spec: Inworld AI Runtime WebSocket APIsOperations: 2Messages: 8
Channel address
/stt/v1/transcribe:streamBidirectional
Operations
publish
sttClientMessage
Messages sent from client to Inworld STT.
subscribe
sttServerMessage
Messages streamed from Inworld STT to the client.
Messages
stt.transcribeConfig
Transcribe config (client, first message)
Content-Type:
stt.audioChunk
Audio chunk (client)
Content-Type:
stt.endTurn
End turn (client)
Content-Type:
stt.closeStream
Close stream (client)
Content-Type:
stt.transcription
Transcription (server)
Content-Type:
stt.speechStarted
Speech started (server)
Content-Type:
stt.speechStopped
Speech stopped (server)
Content-Type:
stt.usage
Usage (server, coming soon)
Content-Type:
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.