AsyncAPI channel · OpenADR Alliance · OpenADR 3 Object Operation Notifications

{topic}

A VTN-assigned MQTT topic carrying notifications for one object type and one operation (or ALL). Resolve the concrete name from notifierTopicsResponse.topics.{CREATE|UPDATE|DELETE|ALL} returned by the matching GET /notifiers/mqtt/topics/* operation. The specification example pattern is "{objectType}s/create", "{objectType}s/update", "{objectType}s/delete", "{objectType}s/+", but a VTN may name top

Open source AsyncAPI → All OpenADR Alliance channels OpenADR Alliance provider profile
Provider: OpenADR Alliance AsyncAPI: v3.0.0 Spec: OpenADR 3 Object Operation Notifications Operations: 1 Messages: 1

Channel address

{topic}

Parameters

Operations

receive
receiveMqttNotification
The subscriber consumes JSON-serialized notifications from a VTN-assigned topic. Target-based filtering is not available on this binding; object privacy is enforced by VEN-scoped topics instead.

Messages

objectOperationNotification
VTN generated object included in request to subscription callbackUrl.
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.