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 ``. All events listed below flow over this same connection.
Initial stream metadata sent by Plivo on connection.
Content-Type: application/json
media
Base64-encoded raw audio chunk from the live call.
Content-Type: application/json
dtmf
A DTMF digit detected on the live call.
Content-Type: application/json
playedStream
Acknowledgement that playback has reached a named checkpoint.
Content-Type: application/json
clearedAudio
Acknowledgement that buffered playback audio was cleared.
Content-Type: application/json
playAudio
Server-to-Plivo audio injection during bidirectional streaming.
Content-Type: application/json
checkpoint
Server-to-Plivo playback checkpoint marker.
Content-Type: application/json
clearAudio
Server-to-Plivo request to discard buffered playback audio.
Content-Type: application/json
sendDTMF
Server-to-Plivo request to play DTMF digits into the call.
Content-Type: application/json
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.