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.
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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.