AsyncAPI channel · Knative · Knative Eventing CloudEvents

/broker

CloudEvents are sent to Broker ingress via HTTP POST and delivered to all matching Triggers. Events must conform to the CloudEvents 1.0 specification in either structured JSON or binary encoding.

Open source AsyncAPI → All Knative channels Knative provider profile
Provider: Knative AsyncAPI: v2.6.0 Spec: Knative Eventing CloudEvents Operations: 2 Messages: 3

Channel address

/broker

Operations

publish
sendEventToBroker
Send a CloudEvent to a Broker
receiveEventFromBroker
Receive a CloudEvent from a Broker via Trigger

Messages

KubernetesApiEvent
A CloudEvent emitted by ApiServerSource when a Kubernetes resource event occurs (Added, Modified, or Deleted).
Content-Type: application/json
PingEvent
A CloudEvent emitted by PingSource on a cron schedule with a configurable payload.
Content-Type: application/json
GenericCloudEvent
A generic CloudEvent conforming to the CloudEvents 1.0 specification, used for custom event producers including SinkBinding subjects and custom event sources sending events through Brokers or Channels
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.