AsyncAPI channel · Plivo
· Plivo Audio Streaming WebSocket API
/
Single bidirectional JSON-over-WebSocket channel established when Plivo connects to the customer's WSS endpoint declared in `
Channel address
/
Operations
receive
receiveStart
Stream started
receive
receiveMedia
Inbound audio chunk
receive
receiveDtmf
Caller DTMF key press
receive
receivePlayedStream
Checkpoint reached
receive
receiveClearedAudio
Buffered audio cleared
send
sendPlayAudio
Play audio into the call
send
sendCheckpoint
Mark a playback checkpoint
send
sendClearAudio
Clear buffered playback audio
send
sendDTMF
Send DTMF digits into the call
Messages
start
Initial stream metadata sent by Plivo on connection.
Content-Type:
application/jsonmedia
Base64-encoded raw audio chunk from the live call.
Content-Type:
application/jsondtmf
A DTMF digit detected on the live call.
Content-Type:
application/jsonplayedStream
Acknowledgement that playback has reached a named checkpoint.
Content-Type:
application/jsonclearedAudio
Acknowledgement that buffered playback audio was cleared.
Content-Type:
application/jsonplayAudio
Server-to-Plivo audio injection during bidirectional streaming.
Content-Type:
application/jsoncheckpoint
Server-to-Plivo playback checkpoint marker.
Content-Type:
application/jsonclearAudio
Server-to-Plivo request to discard buffered playback audio.
Content-Type:
application/jsonsendDTMF
Server-to-Plivo request to play DTMF digits into the call.
Content-Type:
application/jsonAbout 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.