AsyncAPI channel · OpenADR Alliance · OpenADR 3 Object Operation Notifications

{callbackUrl}

The callbackUrl registered on each subscription.objectOperations[] entry. Declared in the OpenAPI as the notifyEvent callback on POST /subscriptions with security [{}]. The subscriber may supply a bearerToken alongside the callbackUrl, which the VTN is expected to present on its requests, but that token is not modelled on the callback operation itself and there is no payload signature or replay de

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

{callbackUrl}

Parameters

Operations

receive
receiveWebhookNotification
The VTN POSTs a notification to the subscriber. The subscriber returns 200 to accept it, or a problem document on 400.

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.