AsyncAPI channel · Knative · Knative Eventing CloudEvents

/sink

Event sinks receive CloudEvents from sources like ApiServerSource, PingSource, and SinkBinding via HTTP POST. The sink URL is injected as K_SINK for SinkBinding subjects or specified in source specs.

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

Channel address

/sink

Operations

receiveEventFromSource
Receive a CloudEvent from an event source

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.