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.
Channel address
{dataFormat}/workspaces/{workspaceId}/assets/{assetId}/divisions/{divisionId}/units/{unitId}/signals/{signalId}
Parameters
dataFormat— Serialization format of the stream.workspaceId—assetId—divisionId—unitId—signalId—
Operations
subscribe
streamSignalData
Messages
DataPoint
Signal data point
Content-Type:
application/jsonAbout 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.
Work with this as data
Every channel here is available over the APIs.io API and to AI agents over MCP.