How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Azure Event Hubs Events API

Operations for sending events to Azure Event Hubs, including single events, batch events, partition-specific events, and events with publisher identity.

Azure Event Hubs Events API is one of 10 APIs that Azure Event Hubs publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Event. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 4 operations across 4 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 2014-01.

Requests are made against a single base URL, https://{namespaceName}.servicebus.windows.net.

4 operations 4 paths 4 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2014-01
Base URL
https://management.azure.com
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Azure Event Hubs Events API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (sas_token). It accepts HTTP bearer tokens (JWT) (bearer_token). By default, every request must be authenticated.

  • sas_token — Shared Access Signature token. Format: SharedAccessSignature sr={namespace}.servicebus.windows.net&sig={signature}&se={expiry}&skn={keyName}
  • bearer_token — Azure Active Directory (Azure AD) JSON Web Token (JWT). Format: Bearer {Azure AD JWT token}

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 POST. Each is listed below with its method, path, parameters, and response codes.

Events 4

Operations for sending events to Azure Event Hubs, including single events, batch events, partition-specific events, and events with publisher identity.

POST
/{eventHubPath}/messages
Azure Event Hubs Send event
SendEvent 4 params body → 201401500
POST
/{eventHubPath}/messages?batch=true
Azure Event Hubs Send batch events
SendBatchEvents 4 params body → 201401500
POST
/{eventHubPath}/partitions/{partitionId}/messages
Azure Event Hubs Send partition event
SendPartitionEvent 5 params body → 201401500
POST
/{eventHubPath}/publishers/{publisherId}/messages
Azure Event Hubs Send event with publisher ID
SendEventWithPublisherId 5 params body → 201401500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are BatchEventMessage (3 properties), ErrorResponse (2 properties). Each schema is shown below with its type and property counts.

ErrorResponse
object
Error response from the Event Hubs service.
2 properties
BatchEventPayload
array
An array of event messages for batch sending. Each message must have a Body field. UserProperties can optionally be included per message.
EventBody
The body of an event message. Can be any valid JSON, plain text, or binary data.
BatchEventMessage
object
A single message within a batch of events.
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

microsoft-azure-event-hubs-events-api-openapi.yml Raw ↑

Other APIs Azure Event Hubs publishes across the network.

Azure Event Hubs Messaging API
Azure Event Hubs SDK
Azure Event Hubs Authorization Rules API
Azure Event Hubs Consumer Groups API
Azure Event Hubs Disaster Recovery Configs API
Azure Event Hubs Event Hubs API
Azure Event Hubs Namespaces API
Azure Event Hubs Operations API
Azure Event Hubs Schema Registry API
Where this information came from

This is an independent, third-party profile of Azure Event Hubs Events API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.