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

ActiveStreams

Notifications about streams becoming active or inactive on a topic. Opened with `SubscribeToActiveStreams(topicName)`; the server pushes `ActiveStreamsChanged` events with an action of `AddUpdate` or `Remove`. Closed with `UnsubscribeFromActiveStreams(topicName)`.

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

ActiveStreams

Operations

publish
subscribeToActiveStreams
Invoke hub method to subscribe to active-stream changes.
onActiveStreamsChanged
Receive active-stream change notifications (ActiveStreamsChanged).

Messages

SubscribeToActiveStreams
Client-to-server SignalR invocation to subscribe to active-stream changes.
Content-Type: application/json
ActiveStreamsChanged
A stream was added/updated or removed on the topic.
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.