AsyncAPI channel · Argo · Argo Events

`/eventsource/{namespace}/{eventSourceName}/{eventName}`

Name: /eventsource/{namespace}/{eventSourceName}/{eventName}
Creator: Argo

Internal EventBus channel through which EventSources publish events and Sensors consume them. The EventBus is backed by NATS JetStream or Apache Kafka depending on the EventBus configuration.

Open source AsyncAPI → All Argo channels Argo provider profile

Provider: Argo AsyncAPI: v2.6.0 Spec: Argo Events Operations: 2 Messages: 1

Channel address

/eventsource/{namespace}/{eventSourceName}/{eventName}

Parameters

namespace — Kubernetes namespace of the EventSource.
eventSourceName — Name of the EventSource resource.
eventName — Name of the event within the EventSource.

Operations

publish

publishEventToEventBus

EventSource publishes event to EventBus

consumeEventFromEventBus

Sensor consumes event from EventBus

Messages

CloudEvent

A CloudEvents 1.0 envelope wrapping an Argo Events payload

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.