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

ParameterData

Live time-series parameter data for a subscribed topic / stream / parameter. The client opens the subscription by invoking the hub method `SubscribeToParameter(topicName, streamId, parameterId)` (wildcard `*` is supported for topic, stream, and parameter), and the server pushes a `ParameterDataReceived` event for each matching batch of samples until `UnsubscribeFromParameter(...)` is invoked.

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

ParameterData

Operations

publish
subscribeToParameter
Invoke hub method to subscribe to parameter data.
onParameterDataReceived
Receive pushed parameter data (ParameterDataReceived).

Messages

SubscribeToParameter
Client-to-server SignalR invocation to subscribe to parameter data.
Content-Type: application/json
ParameterDataReceived
A batch of time-series parameter samples 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.