NotificationHubsManagementClient

Name: NotificationHubsManagementClient API
Brand: Azure Notification Hubs Management
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsPush Notificationsoauth228 EndpointsREST

For Agents

Provision Azure Notification Hubs namespaces, hubs, and PNS credentials, and manage SAS authorization rules across 28 ARM operations on the Microsoft.NotificationHubs provider.

Connect the NotificationHubsManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NotificationHubsManagementClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with NotificationHubsManagementClient API.

Check the availability of a namespace name before creating it

Provision notification hub namespaces with SKU and region selection

Create individual notification hubs inside a namespace and configure platform credentials (APNS, FCM, WNS)

Define shared access authorization rules at namespace and hub scope with Listen, Send, or Manage rights

GET STARTED

Start building with NotificationHubsManagementClient API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for NotificationHubsManagementClient, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for NotificationHubsManagementClient, keeping it validated and agent-ready. The Azure Notification Hubs management API exposes 28 operations for provisioning notification hub namespaces, individual hubs, authorization rules, and platform-specific PNS credentials (APNS, GCM/FCM, WNS, MPNS, Baidu, ADM). Use it to set up the infrastructure that delivers cross-platform push notifications to mobile and desktop apps at scale, and to rotate the shared access keys that client SDKs use to register devices and send notifications.

Use Cases

Patterns agents use NotificationHubsManagementClient API for, with concrete tasks.

★ Cross-Platform Push Notification Backend

Stand up the backend that delivers push notifications to an app's iOS, Android, and Windows users. Create a namespace, create one notification hub per environment (dev, staging, prod), upload APNS certificates and FCM/WNS keys, and define Listen and Send authorization rules that the mobile SDK and the application backend use respectively. Once provisioned, the actual send and registration calls happen against the data-plane endpoint, not this management API.

Create namespace 'app-notifications' in westeurope, create a notification hub 'production' inside it, and configure APNS production credentials and FCM credentials

Tenant Isolation in a SaaS App

Provision a separate notification hub per customer tenant in a multi-tenant SaaS application. For each new customer signup an automation creates a hub inside a shared namespace, generates per-tenant Listen and Send authorization rules, and returns the connection strings that the tenant's mobile clients and backend will use. This isolates push registrations and audit trails per tenant without spinning up a new namespace for each one.

Create a new notification hub for tenant 'acme-corp' inside the shared namespace, generate Listen and Send authorization rules, and return both connection strings

Credential Rotation and Key Management

Rotate the SAS keys on notification hub authorization rules on a fixed schedule, or in response to a suspected leak. The regenerateKeys operation rotates either the primary or secondary key on a named rule, letting an automation roll the unused key first, update clients to use the new key, then rotate the second key on the next cycle. This keeps push delivery uninterrupted while honouring rotation policy.

Regenerate the SecondaryKey on the DefaultFullSharedAccessSignature rule of the production hub, retrieve the new connection string, and report it back for client deployment

AI Agent Push Notification Operator

An AI agent in a developer tools workflow can provision and rotate notification hubs through Jentic. The agent searches by intent ('create an azure notification hub'), Jentic returns the NotificationHubs_CreateOrUpdate operation with its schema, and the agent executes the call with managed Azure credentials. Hub teardown, key rotation, and credential updates run through the same intent-driven flow.

Search Jentic for 'create an Azure notification hub', load the NotificationHubs_CreateOrUpdate schema, and execute it for hub 'mobile-prod' with APNS credentials

Key Endpoints

28 endpoints — jentic publishes the only available openapi specification for notificationhubsmanagementclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/subscriptions/{subscriptionId}/providers/Microsoft.NotificationHubs/checkNamespaceAvailability

Check if a namespace name is available

GET

/subscriptions/{subscriptionId}/providers/Microsoft.NotificationHubs/namespaces

List all notification hub namespaces in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NotificationHubs/namespaces

List namespaces in a resource group

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NotificationHubs/namespaces/{namespaceName}

Get a notification hub namespace

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NotificationHubs/namespaces/{namespaceName}/AuthorizationRules

List authorization rules on a namespace

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NotificationHubs/namespaces/{namespaceName}/AuthorizationRules/{authorizationRuleName}/listKeys

List connection strings for an authorization rule

GET

/providers/Microsoft.NotificationHubs/operations

List Microsoft.NotificationHubs provider operations

POST

/subscriptions/{subscriptionId}/providers/Microsoft.NotificationHubs/checkNamespaceAvailability

Check if a namespace name is available

GET

/subscriptions/{subscriptionId}/providers/Microsoft.NotificationHubs/namespaces

List all notification hub namespaces in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NotificationHubs/namespaces

List namespaces in a resource group

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NotificationHubs/namespaces/{namespaceName}

Get a notification hub namespace

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NotificationHubs/namespaces/{namespaceName}/AuthorizationRules

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure service principal credentials are encrypted in the Jentic vault. Agents receive scoped ARM bearer tokens at execution time and never see the client secret. Notification hub SAS connection strings retrieved through listKeys are returned only to the calling agent.

Intent-based discovery

Agents search by intent ('create an azure notification hub' or 'rotate notification hub keys') and Jentic returns the matching operation, avoiding the need to learn the 28 endpoints under Microsoft.NotificationHubs.

Time to first call

Direct ARM integration: half a day for AAD app registration, MSAL token handling, and notification hub payload modelling. Through Jentic: under 30 minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure Service Bus

Run alongside Notification Hubs as the underlying messaging fabric for fan-out scenarios.

Use Service Bus when you need queueing or pub/sub between services; Notification Hubs targets device push specifically.

Alternative

Azure Event Grid

Event routing service useful for system-to-system push rather than mobile device push.

Choose Event Grid for cloud event routing; choose Notification Hubs for end-user device notifications.

Alternative

Azure IoT Hub

Bidirectional messaging for IoT devices instead of consumer push notifications.

Choose IoT Hub when targets are sensors and devices; choose Notification Hubs when targets are user-facing apps.

FAQs

Specific to using NotificationHubsManagementClient API through Jentic.

Why is there no official OpenAPI spec for NotificationHubsManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call NotificationHubsManagementClient via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Azure Notification Hubs management API use?

It uses Azure Active Directory OAuth 2.0 against https://management.azure.com/ with the user_impersonation scope. The caller needs Contributor or a custom role with Microsoft.NotificationHubs/* permissions on the resource group. Jentic stores service principal credentials encrypted and issues short-lived bearer tokens at execution time.

Can I send a push notification through this API?

No. This is the management API for provisioning hubs and rotating keys. Actual push notification sends happen against the data-plane endpoint (https://{namespace}.servicebus.windows.net/{hub}/messages) using the SAS connection strings retrieved here, typically via the Notification Hubs SDK or REST.

What are the rate limits for the Notification Hubs management API?

Azure Resource Manager applies subscription-level throttling at roughly 1,200 reads and 1,200 writes per hour. Hub creation and namespace creation are typically synchronous sub-second operations, so you rarely hit the limit during normal provisioning.

How do I create a notification hub through Jentic?

Run pip install jentic and search for 'create an azure notification hub'. Jentic returns the NotificationHubs_CreateOrUpdate operation; load its schema and execute it with the namespace name, hub name, and any APNS or FCM credentials you want set at create time.

How do I rotate a notification hub authorization key?

POST to /subscriptions/{id}/resourceGroups/{rg}/providers/Microsoft.NotificationHubs/namespaces/{ns}/AuthorizationRules/{rule}/regenerateKeys with PolicyKey set to PrimaryKey or SecondaryKey. Rotate the unused key first, update clients, then rotate the other to keep delivery uninterrupted.