AsyncAPI channel · cumulocity
· Cumulocity Notification 2.0 WebSocket
/notification2/consumer
WebSocket consumer. Connection URL is `wss://{tenant}.cumulocity.com/notification2/consumer/?token={jwt}`. Server pushes notifications as JSON frames; consumer ACKs by message id.
Channel address
/notification2/consumer
Operations
publish
ackNotification
Acknowledge a notification by its message id so the server can advance the per-subscriber cursor.
subscribe
consumeNotifications
Receive notifications for the subscriptions associated with the JWT token.
Messages
ack
Notification Acknowledgement
Content-Type:
managedObjectNotification
Managed Object Notification
Content-Type:
measurementNotification
Measurement Notification
Content-Type:
eventNotification
Event Notification
Content-Type:
alarmNotification
Alarm Notification
Content-Type:
operationNotification
Operation Notification
Content-Type:
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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.