AsyncAPI channel · Quix · Quix Streaming Reader API (SignalR / WebSocket)

EventData

Live discrete events for a subscribed topic / stream / event. Opened with hub method `SubscribeToEvent(topicName, streamId, eventId)`; the server pushes `EventDataReceived` events. Closed with `UnsubscribeFromEvent(...)`.

Open source AsyncAPI → All Quix channels Quix provider profile
Provider: Quix AsyncAPI: v2.6.0 Spec: Quix Streaming Reader API (SignalR / WebSocket) Operations: 2 Messages: 2

Channel address

EventData

Operations

publish
subscribeToEvent
Invoke hub method to subscribe to event data.
onEventDataReceived
Receive pushed event data (EventDataReceived).

Messages

SubscribeToEvent
Client-to-server SignalR invocation to subscribe to event data.
Content-Type: application/json
EventDataReceived
A discrete event pushed by the hub.
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.