How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Weidmüller u-OS Data Hub Variable-NATS API

A fast asynchronous, event-based NATS API for providing and consuming variables within the u-OS Data Hub; not accessible to clients outside the device (AsyncAPI 2.6.0, 10 channels, NATS server at 127.0.0.1:49360 on the device).

Weidmüller u-OS Data Hub Variable-NATS API is one of 16 APIs that Weidmüller publishes on the APIs.io network, described by an AsyncAPI event-driven specification.

Tagged areas include Data Hub, NATS, Event-Driven, and u-OS. The published artifact set on APIs.io includes an AsyncAPI specification.

This event API exposes 14 operations across 10 channels, and defines 19 schemas. It is described by AsyncAPI 2.6.0, at version 1.0.1.

The API connects through a single server, 127.0.0.1:49360 (NATS).

14 operations 10 channels 19 schemas

Metadata

The identity and technical contract details declared by the specification.

Specification
AsyncAPI 2.6.0
API Version
1.0.1
Server
127.0.0.1:49360 (NATS)
License
MIT
Resource Areas
1

Channels & Operations 14

Across 10 channels, the API surfaces 14 operations. Each is listed below with its action, channel, parameters, and response codes.

Channels 14
SUB
v1.loc.{providerId}.vars.evt.changed
A consumer subscribes to this subject to be informed about variable value changes. The consumer receives an event with a list of all variables whose value or quality has changed. The consumer must fi…
receiveVariablesChangedEvent 1 param body
PUB
v1.loc.{providerId}.vars.evt.changed
A provider publishes its list of variables, if they have changed their value or quality.
emitVariablesChangedEvent 1 param body
SUB
v1.loc.{providerId}.vars.qry.read
A provider subscribes to this subject in order to receive read variable queries for its variables. It receives Nats requests on this subject and responds via the response subject supplied in the requ…
receiveReadVariablesQueryRequest 1 param body
PUB
v1.loc.{providerId}.vars.qry.read
A consumer publishes a request for reading a list of provider variables.
emitReadVariablesQueryRequest 1 param body
SUB
v1.loc.{providerId}.vars.cmd.write
A provider subscribes to this subject to receive write variables commands for its variables.
receiveWriteVariablesCommand 1 param body
PUB
v1.loc.{providerId}.vars.cmd.write
A consumer publishes a command to write a list of provider variables.
emitWriteVariablesCommand 1 param body
PUB
v1.loc.{providerId}.def.evt.changed
A provider publishes the changed provider definition.
emitProviderDefinitionChangedEvent 1 param body
PUB
v1.loc.registry.providers.{providerId}.def.qry.read
A consumer queries a provider's definition.
emitReadProviderDefinitionQueryRequest 1 param body
SUB
v1.loc.registry.providers.{providerId}.def.evt.changed
A client subscribes to changes of a provider definition. If a change occurs, the client receives an event with the updated provider definition. Consumers shall refresh the variable list. Both consume…
receiveProviderDefinitionChangedEvent 1 param body
PUB
v1.loc.registry.providers.qry.read
A consumer requests a list of providers.
emitReadProvidersQueryRequest body
SUB
v1.loc.registry.providers.evt.changed
A consumer subscribes to this subject to get notified about available providers in the system.
receiveProvidersChangedEvent body
SUB
v1.loc.registry.state.evt.changed
A client that has subscribed to this event receives a message when the state of the registry has changed. If a provider receives a 'registry up' event via this subject, it shall resend its provider d…
receiveStateChangedEvent body
SUB
_INBOX.{consumerName}.{sessionId}
A client subscribes to this subject in order to receive the response to its queries. If the client uses the NATS request function, NATS takes care of subscribing to the correct subject.
replyFromProvider 2 params
PUB
_INBOX.{consumerName}.{sessionId}
A client publishes the response to a query on this subject. The exact subject for the query is encoded in the request. If the client uses the NATS respond function, NATS automatically uses the correc…
replyFromConsumer 2 params body

Messages & Schemas 19

The contract defines 19 schemas that model the data carried by its messages. The most detailed are ResponseHeaders (2 properties), Headers (1 property). Each schema is shown below with its type and property counts.

ProviderDefinitionChangedEvent
message
ProvidersChangedEvent
message
ReadProviderDefinitionQueryRequest
message
ReadProviderDefinitionQueryResponse
message
ReadProvidersQueryRequest
message
ReadProvidersQueryResponse
message
ReadVariablesQueryRequest
message
ReadVariablesQueryResponse
message
StateChangedEvent
message
VariablesChangedEvent
message
WriteVariablesCommand
message
Duration
object
Headers
object
1 property
ProviderDefinition
object
ProviderList
object
ResponseHeaders
object
2 properties
State
object
Timestamp
object
VariableList
object

Specification

The full machine-readable AsyncAPI contract behind this narrative.

Source

weidmueller-variable-nats-asyncapi.yml Raw ↑

Other APIs Weidmüller publishes across the network.

Weidmüller Consumer API
Weidmüller Firewall API
Weidmüller Logging API
Weidmüller Network API
Weidmüller Operations API
Weidmüller Ping API
Weidmüller Realtime API
Weidmüller Recovery API
Weidmüller Security API
Weidmüller Serial Interfaces API
Weidmüller Syslog API
Weidmüller System API
Where this information came from

This is an independent, third-party profile of Weidmüller u-OS Data Hub Variable-NATS API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.