AsyncAPI channel · DeepL · DeepL Voice API - WebSocket Streaming

/v1/voice/realtime/connect?token={token}

Bidirectional channel for streaming source audio chunks to DeepL and receiving incremental source-language transcriptions, translated transcriptions, and (closed beta) synthesized translated audio.

Provider: DeepL AsyncAPI: v3.0.0 Spec: DeepL Voice API - WebSocket Streaming Operations: 2 Messages: 10

Channel address

/v1/voice/realtime/connect?token={token}

Parameters

Operations

send
sendAudioData
Send a source-audio chunk or end-of-source signal to DeepL.
receive
receiveTranscriptions
Receive transcriptions, translations, synthesized audio, and lifecycle events.

Messages

source_media_chunk
Chunk of audio data from the client.
Content-Type:
end_of_source_media
Client signals it has finished sending source audio.
Content-Type:
source_transcript_update
Incremental source-language transcription (concluded + tentative segments).
Content-Type:
target_transcript_update
Incremental target-language translation (concluded + tentative segments).
Content-Type:
target_media_chunk
Synthesized translated audio (closed beta).
Content-Type:
end_of_source_transcript
Content-Type:
end_of_target_transcript
Content-Type:
end_of_target_media
Content-Type:
end_of_stream
Server indicates all processing is complete; safe to close the connection.
Content-Type:
error
Processing error reported by the server.
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.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.

Work with this as data

Every channel here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for event channels

4 MCP tools reach this
  • find_channelsBrowse and filter every channel in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This channel
curl "https://apis.io/api/v1/channels/v1-voice-realtime-connect-token-token"
All event channels
curl "https://apis.io/api/v1/channels?limit=25"

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.

A second provider on the same verified email joins the account you already have.