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.
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
subscribe
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.
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.