AsyncAPI channel · Beam · Beam Realtime Endpoints (WebSocket)

/

The realtime WebSocket channel. After the client opens the connection (authenticating with a Beam Bearer token), it may publish input messages and subscribe to output messages streamed back from the deployed handler.

Open source AsyncAPI → All Beam channels Beam provider profile
Provider: Beam AsyncAPI: v2.6.0 Spec: Beam Realtime Endpoints (WebSocket) Operations: 2 Messages: 2

Channel address

/

Operations

publish
sendRealtimeInput
Send an input payload to the deployed realtime handler.
receiveRealtimeOutput
Receive output payloads streamed from the realtime handler.

Messages

RealtimeInput
A JSON payload sent from the client into the deployed handler.
Content-Type: application/json
RealtimeOutput
A JSON payload streamed from the handler back to the client.
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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.