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 Grid Namespace Topics API

Namespace topic publish, receive, acknowledge

Azure Event Grid Namespace Topics API is one of 3 APIs that Azure Event Grid publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Namespace Topics. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 5 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 2018-01-01.

Requests are made against a single base URL, https://{topic-endpoint}.

5 operations 5 paths 1 schemas 5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2018-01-01
Base URL
https://{topic-endpoint}.{region}.eventgrid.azure.net
Authentication
API Key, API Key, OAuth 2.0
Resource Areas
1

Authentication & Security 3

Azure Event Grid Namespace Topics API declares 3 security schemes for authenticating requests. An API key is passed in the header as aeg-sas-key (sasKey). An API key is passed in the header as aeg-sas-token (sasToken). It supports OAuth 2.0 (entra) using the clientCredentials flow, exposing 1 scope.

  • sasKey — Topic shared-access key
  • sasToken — Topic shared-access signature token
  • entra — Microsoft Entra ID OAuth 2.0 bearer token

Paths & Operations 5

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

Namespace Topics 5

Namespace topic publish, receive, acknowledge

POST
/topics/{topicName}:publish
Publish CloudEvents to a namespace topic
publishToNamespaceTopic 2 params body → 200
POST
/topics/{topicName}/subscriptions/{subscriptionName}:receive
Receive a batch of CloudEvents from a namespace topic subscription
receiveEvents 5 params → 200
POST
/topics/{topicName}/subscriptions/{subscriptionName}:acknowledge
Acknowledge events from a namespace topic subscription
acknowledgeEvents 3 params body → 200
POST
/topics/{topicName}/subscriptions/{subscriptionName}:release
Release locked events back to the queue
releaseEvents 3 params body → 200
POST
/topics/{topicName}/subscriptions/{subscriptionName}:reject
Reject (dead-letter) locked events
rejectEvents 3 params body → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is CloudEvent (9 properties). Each schema is shown below with its type and property counts.

CloudEvent
object
9 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

azure-event-grid-namespace-topics-api-openapi.yml Raw ↑

Other APIs Azure Event Grid publishes across the network.

Azure Event Grid Publisher API
Azure Event Grid Publish API
Where this information came from

This is an independent, third-party profile of Azure Event Grid Namespace Topics 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.