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.

Open source AsyncAPI → All Plivo channels Plivo provider profile
Provider: Plivo AsyncAPI: v3.0.0 Spec: Plivo Audio Streaming WebSocket API Operations: 9 Messages: 9

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/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.

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/audiostream"
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.

GitHub Google LinkedIn

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