AsyncAPI channel · Inworld AI · Inworld AI Runtime WebSocket APIs

/api/v1/realtime/session

Bidirectional WebSocket endpoint for Inworld Realtime sessions. The protocol is intentionally compatible with the OpenAI Realtime API event protocol; existing OpenAI Realtime clients can connect by changing the base URL and authentication header. Inworld extends the session object with a `providerData` field for STT, TTS, memory, backchannel, and responsiveness extensions (see https://docs.inworld

Open source AsyncAPI → All Inworld AI channels Inworld AI provider profile
Provider: Inworld AI AsyncAPI: v2.6.0 Spec: Inworld AI Runtime WebSocket APIs Operations: 2 Messages: 14

Channel address

/api/v1/realtime/session

Parameters

Operations

publish
realtimeClientEvent
Events sent from client to the Realtime session.
realtimeServerEvent
Events streamed from the Realtime session back to the client.

Messages

session.update
session.update (client)
Content-Type:
conversation.item.create
conversation.item.create (client)
Content-Type:
conversation.item.truncate
conversation.item.truncate (client)
Content-Type:
conversation.item.delete
conversation.item.delete (client)
Content-Type:
conversation.item.retrieve
conversation.item.retrieve (client)
Content-Type:
response.create
response.create (client)
Content-Type:
response.cancel
response.cancel (client)
Content-Type:
input_audio_buffer.append
input_audio_buffer.append (client)
Content-Type:
input_audio_buffer.commit
input_audio_buffer.commit (client)
Content-Type:
input_audio_buffer.clear
input_audio_buffer.clear (client)
Content-Type:
output_audio_buffer.clear
output_audio_buffer.clear (client)
Content-Type:
session.created
session.created (server)
Content-Type:
session.updated
session.updated (server)
Content-Type:
realtime.server_event
Inworld documents additional server events that follow the OpenAI Realtime API protocol — including (non-exhaustive) `response.start`, `response.content_part.added`, `response.content_part.delta`, `re
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/api-v1-realtime-session"
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.