Microsoft Azure EventGridManagementClient
Browse all Azure APIsAgent-ready OpenAPI document · curated by JenticCloud InfrastructureServerlessoauth240 EndpointsREST
Know of an official OpenAPI document? Contribute it →
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.
Use for: I need to create an Event Grid topic for my custom application events, Add an event subscription that POSTs to my webhook when blob events fire, Rotate the access keys on an Event Grid topic, List every event subscription on a topic
Not supported: Does not publish events, run subscriber compute, or process delivery retries - use for Event Grid topic, domain, and subscription management only.
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.
Install Jentic One Beta
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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-eventgrid-management" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-eventgrid-management" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Discover topic types and the event types each one publishes
List event subscriptions globally or filtered by region or topic type
Delete a topic, domain, or subscription cleanly when retiring an integration
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 your Jentic One instance.
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
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
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Event Grid management by hand means handling Azure AD OAuth 2.0 tokens against management.azure.com, building the Microsoft.EventGrid ARM paths for topics, domains, and subscriptions, polling the async long-running operation on subscription creation, and managing the webhook validation handshake. Through Jentic you install once, import EventGridManagementClient from the API Directory, store the Azure AD client credentials once, and your agent calls it.
Permission scoping
Event Grid puts the subscription, resource group, and topic or domain name in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventGrid/topics/{topicName}/...), so a rule can pin your agent to one topic or domain. You choose the operations it may call, so destructive ones like Topics_Delete or Domains_RegenerateKey are not included unless you add them.
Credential isolation
Your Azure AD client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time as a scoped bearer token. The underlying secret and any shared access keys returned by ListSharedAccessKeys never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create an azure event subscription' or 'rotate an Event Grid access key', and Jentic returns the matching Topics, Domains, or EventSubscriptions operation with its input schema so the agent calls the right endpoint without browsing the ARM reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 with Jentic One, the self-hosted execution layer.
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 your Jentic One instance 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.
Can I limit what my agent is allowed to do with the Microsoft Azure Event Grid Management Client API?
Yes. Because you self-host Jentic One, your own rules decide which Event Grid operations and credentials the agent may use. Since the subscription, resource group, and topic or domain name live in the ARM URL path, you can pin the agent to a single topic or domain, and you choose the exact operations it may call, so destructive ones like Topics_Delete or Domains_RegenerateKey are excluded unless you add them. Your Azure AD client secret and any shared access keys returned by ListSharedAccessKeys stay inside your own instance and never reach the agent's prompt or logs.
GET STARTED