AsyncAPI channel · Nortech · Nortech Live Data (MQTT)

{dataFormat}/workspaces/{workspaceId}/assets/{assetId}/divisions/{divisionId}/units/{unitId}/signals/{signalId}

Per-signal live data stream. dataFormat is "json" or "protobuf". Single-level wildcards (+) are not supported.

Open source AsyncAPI → All Nortech channels Nortech provider profile
Provider: Nortech AsyncAPI: v2.6.0 Spec: Nortech Live Data (MQTT) Operations: 1 Messages: 1

Channel address

{dataFormat}/workspaces/{workspaceId}/assets/{assetId}/divisions/{divisionId}/units/{unitId}/signals/{signalId}

Parameters

Operations

streamSignalData

Messages

DataPoint
Signal data point
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.