EventGridManagementClient

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureServerlessoauth240 EndpointsREST

For Agents

Manage Azure Event Grid topics, domains, and event subscriptions; rotate shared access keys; and discover topic and event types for routing Azure events to webhooks and serverless consumers.

Connect the EventGridManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EventGridManagementClient, 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 EventGridManagementClient API.

Create or update an Event Grid topic in a chosen region

Create or update an Event Grid domain to fan out events to many topics

Manage event subscriptions that deliver events to a webhook, Function, or queue

List shared access keys for a topic or domain and regenerate them on demand

GET STARTED

Start building with EventGridManagementClient API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for EventGridManagementClient, keeping it validated and agent-ready. The Azure EventGrid Management Client is the control-plane API for Azure Event Grid — the fully managed event routing service that fans Azure resource events out to webhooks, Azure Functions, Logic Apps, and other subscribers. It exposes 40 endpoints covering custom topics, domains, domain topics, event subscriptions (global, regional, and per-topic-type), shared access keys, and topic type discovery.

Use Cases

Patterns agents use EventGridManagementClient API for, with concrete tasks.

★ Custom Application Event Bus

Engineering teams use Event Grid as the backbone for an internal event bus — services publish domain events to a topic, and downstream subscribers (Functions, Logic Apps, webhooks) consume them. The API exposes Topics_CreateOrUpdate and EventSubscriptions_CreateOrUpdate, so a deployment pipeline can stand up the topic, wire each subscriber, and rotate access keys without anyone touching the portal.

Create an Event Grid topic named orders in resource group prod-rg, then add an event subscription named ordersFn pointing at an Azure Function URL with eventDeliverySchema=EventGridSchema.

Domain-Per-Tenant Event Routing

SaaS platforms with many tenants use Event Grid domains to multiplex events: each tenant gets a domain topic inside a single domain resource, and the platform fans events through one endpoint with per-tenant authorisation. The API supports this with Domains_CreateOrUpdate, DomainTopics_CreateOrUpdate, and EventSubscriptions_CreateOrUpdate scoped to the domain topic — supporting thousands of tenants without one resource per tenant.

Create an Event Grid domain named platform in resource group prod-rg, add a domain topic named tenant-42, and attach an event subscription pointing at the tenant's webhook.

Access Key Rotation for Event Grid Endpoints

Security policy commonly requires shared-access keys to rotate every 90 days. EventGrid exposes Topics_ListSharedAccessKeys, Topics_RegenerateKey, Domains_ListSharedAccessKeys, and Domains_RegenerateKey — so a scheduled agent can rotate keys, update consuming applications via a deployment, and confirm the new value is live without portal access.

Call Topics_RegenerateKey for the secondary key on topic orders in resource group prod-rg, then update the consuming application's secret store with the new value.

AI Agent Event Wiring via Jentic

An infrastructure agent integrated through Jentic can resolve a request like wire blob created events on this storage account into the orders processing function end-to-end. It searches Jentic for create azure event subscription, loads EventSubscriptions_CreateOrUpdate, supplies the source resource ID and webhook destination, and confirms provisioning. Credentials never leave the Jentic vault.

Through Jentic, search for create an azure event subscription, load EventSubscriptions_CreateOrUpdate, and create a subscription on the storage account that POSTs blob created events to the orders Function URL.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventGrid/domains/{domainName}

Create or update an Event Grid domain

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventGrid/domains/{domainName}/topics/{domainTopicName}

Create or update a domain topic

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventGrid/domains/{domainName}/listKeys

List shared access keys for a domain

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventGrid/domains/{domainName}/regenerateKey

Regenerate a shared access key for a domain

GET

/providers/Microsoft.EventGrid/topicTypes

List topic types Event Grid supports

GET

/providers/Microsoft.EventGrid/topicTypes/{topicTypeName}/eventTypes

List event types for a topic type

GET

/subscriptions/{subscriptionId}/providers/Microsoft.EventGrid/topics

List Event Grid topics in a subscription

GET

/subscriptions/{subscriptionId}/providers/Microsoft.EventGrid/eventSubscriptions

List global event subscriptions in a subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventGrid/domains/{domainName}

Create or update an Event Grid domain

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventGrid/domains/{domainName}/topics/{domainTopicName}

Create or update a domain topic

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventGrid/domains/{domainName}/listKeys

List shared access keys for a domain

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventGrid/domains/{domainName}/regenerateKey

Regenerate a shared access key for a domain

GET

/providers/Microsoft.EventGrid/topicTypes

Why though Jentic?

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

Credential isolation

Azure AD client credentials are stored encrypted in the Jentic vault (MAXsystem). The agent receives a short-lived bearer token scoped to management.azure.com — the underlying secret stays out of agent context. Topic-level access keys returned by ListSharedAccessKeys are also held in Jentic, never in the agent.

Intent-based discovery

Agents search by intent (e.g. 'create an azure event subscription' or 'event grid topic') and Jentic returns the matching Topics_*, Domains_*, or EventSubscriptions_* operation along with its full input schema, so the agent picks the right endpoint without browsing ARM docs.

Time to first call

Direct integration: 1-2 days for AAD auth, async LRO polling on subscription creation, and webhook validation handshake handling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Diagnostics API Client

Diagnose App Service workloads that may consume Event Grid events

Use when the agent needs to investigate a webhook subscriber that is not receiving events

Complementary

EngagementFabric

Manage customer engagement channels that often subscribe to Event Grid topics

Use when the agent needs to wire engagement channels to event subscribers

Alternative

Disk Resource Provider Client

Manages Azure managed disks rather than event routing

Choose when the request is about VM storage rather than event distribution

FAQs

Specific to using EventGridManagementClient API through Jentic.

Why is there no official OpenAPI spec for EventGridManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call EventGridManagementClient 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 EventGridManagementClient use?

It uses Azure Active Directory OAuth 2.0 (azure_auth) against https://management.azure.com/. The principal needs at least EventGrid Contributor or Contributor on the target resource group. Through Jentic the underlying client secret stays in the Jentic vault and the agent only sees a scoped bearer token.

Can I create an event subscription on any Azure resource?

Event Subscriptions can target any Azure resource that emits events through Event Grid (storage accounts, resource groups, custom topics, domains, etc.). PUT on the event subscription endpoint accepts the source resource scope in the URL and the destination (webhook, Azure Function, Service Bus queue, hybrid connection, storage queue) in the body.

What are the rate limits for the EventGridManagementClient?

Standard Azure Resource Manager subscription-scoped throttling applies (broadly 12,000 reads per hour and 1,200 writes per hour). Event Grid itself enforces per-topic publish-rate limits separately on the data plane — confirm topic capacity before designing high-throughput publishers.

How do I subscribe a webhook to topic events through Jentic?

Run pip install jentic, search for create an azure event subscription, load EventSubscriptions_CreateOrUpdate, supply scope (the topic resource ID), eventSubscriptionName, and a destination object with endpointType=WebHook and the webhook URL, then execute. The response is the subscription with its provisioningState.

Does this API publish events to a topic?

No. EventGridManagementClient is a control-plane API for managing topics, domains, and subscriptions. Publishing events is a data-plane operation against the topic endpoint URL using the access key returned by Topics_ListSharedAccessKeys.