AsyncAPI channel · Discord
· Discord Voice API
/
Channel address
/
Operations
publish
sendVoiceMessage
Send message to voice server
subscribe
receiveVoiceEvent
Receive events from voice server
Messages
VoiceIdentify
Begin a voice WebSocket connection
Content-Type:
SelectProtocol
Select the voice protocol and provide connection details
Content-Type:
VoiceHeartbeat
Sent periodically to maintain the voice connection
Content-Type:
Speaking
Indicate speaking status
Content-Type:
VoiceResume
Resume a voice connection
Content-Type:
VoiceReady
Voice server is ready, provides connection information
Content-Type:
SessionDescription
Voice session description with encryption details
Content-Type:
VoiceHeartbeatAck
Acknowledgment of a voice heartbeat
Content-Type:
VoiceHello
Received after connecting, contains heartbeat interval
Content-Type:
VoiceResumed
Voice connection successfully resumed
Content-Type:
ClientDisconnect
A user disconnected from the voice channel
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.