AsyncAPI channel · wasmCloud · wasmCloud Control Interface API

wasmbus.ctl.v1.{lattice}.evt.{hostId}

Event stream published by wasmCloud hosts for observability. Hosts emit structured CloudEvents-formatted events for all significant lifecycle changes including component start/stop, provider start/stop, link changes, and health check results.

Open source AsyncAPI → All wasmCloud channels wasmCloud provider profile
Provider: wasmCloud AsyncAPI: v2.6.0 Spec: wasmCloud Control Interface API Operations: 1 Messages: 5

Channel address

wasmbus.ctl.v1.{lattice}.evt.{hostId}

Parameters

Operations

receiveHostEvent
Receive a wasmCloud host lifecycle event

Messages

ComponentScaledEvent
CloudEvent emitted when a component's replica count changes
Content-Type: application/json
ProviderStartedEvent
CloudEvent emitted when a capability provider successfully starts
Content-Type: application/json
ProviderStoppedEvent
CloudEvent emitted when a capability provider stops
Content-Type: application/json
LinkdefSetEvent
CloudEvent emitted when a link definition is created or updated
Content-Type: application/json
HostHeartbeatEvent
Periodic heartbeat event emitted by each wasmCloud host
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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.