AsyncAPI channel · Spring WebFlux · Spring WebFlux WebSocket API

/ws

WebSocket channel mapped via Spring WebFlux WebSocketHandlerAdapter. A WebSocketSession is established on connection and provides reactive inbound() and outbound() message streams.

Provider: Spring WebFlux AsyncAPI: v3.0.0 Spec: Spring WebFlux WebSocket API Operations: 4 Messages: 5

Channel address

/ws

Operations

send
sendTextMessage
Send Text Message
receive
receiveTextMessage
Receive Text Message
send
sendBinaryMessage
Send Binary Message
receive
receiveBinaryMessage
Receive Binary Message

Messages

TextMessage
A UTF-8 encoded text data frame (opcode 0x1)
Content-Type: text/plain
BinaryMessage
A binary data frame (opcode 0x2)
Content-Type: application/octet-stream
PingMessage
A control ping frame (opcode 0x9) for keep-alive
Content-Type:
PongMessage
A control pong frame (opcode 0xA) in response to ping
Content-Type:
CloseMessage
A control close frame (opcode 0x8) to initiate connection closure
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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.