AsyncAPI channel · Azure Event Hubs · Azure Event Hubs Messaging API

`{eventHubName}/partitions/{partitionId}`

Name: {eventHubName}/partitions/{partitionId}
Creator: Azure Event Hubs

A partition-specific channel for publishing events to a specific partition of an event hub. Using partition-targeted publishing gives you direct control over which partition receives the event but bypasses the load balancing that Event Hubs provides.

Open source AsyncAPI → All Azure Event Hubs channels Azure Event Hubs provider profile

Provider: Azure Event Hubs AsyncAPI: v2.6.0 Spec: Azure Event Hubs Messaging API Operations: 2 Messages: 2

Channel address

{eventHubName}/partitions/{partitionId}

Parameters

eventHubName — The name of the event hub.
partitionId — The partition identifier. Partition IDs are zero-based integers (e.g., 0, 1, 2, ..., N-1 where N is the partition count).

Operations

publish

publishPartitionEvent

Publish event to specific partition

consumePartitionEvent

Consume events from specific partition

Messages

EventMessage

An event published to Azure Event Hubs.

Content-Type: application/json

ReceivedEventMessage

An event received from Azure Event Hubs.

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.