Microsoft Azure Azure API Management Client
Browse all Azure APIs43
AI ReadinessFoundational (D-)43/100
Agent-ready OpenAPI document · curated by JenticDeveloper ToolsMonitoring Observabilityoauth213 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Provision, back up, restore, and inspect Azure API Management service instances at the deployment level.
Use for: List all Azure API Management services in subscription 1111-2222-3333-4444, Check whether the API Management service name 'contoso-apim' is available, Get the details of API Management service 'contoso-apim' in resource group 'rg-prod', Back up API Management service 'contoso-apim' to storage account contosobackups
Not supported: Does not manage APIs, products, policies, subscriptions, or developer accounts inside an APIM instance - use only for the deployment-level service lifecycle.
Jentic publishes the only available OpenAPI specification for Azure API Management Client, keeping it validated and agent-ready. This deployment-level surface manages Azure API Management service instances themselves: list services in a subscription or resource group, get service details, check name availability, run backups and restores, apply network configuration updates, and obtain SSO tokens for the management portal. The product-level operations on APIs, products, and policies live on adjacent APIM clients.
Install Jentic One Beta
Connect the Azure API Management Client to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure API Management Client, 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%2Fapi-management-client" | 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%2Fapi-management-client" | 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 Azure API Management Client API.
List API Management services across a subscription or within a resource group
Check whether a proposed API Management service name is available
Back up an API Management service to a storage account
Restore an API Management service from a previous backup
Apply queued network configuration updates to a service
Obtain an SSO token for the API Management developer portal
Use Cases
Patterns agents use Azure API Management Client API for, with concrete tasks.
★ Disaster Recovery Backups
Operations teams schedule regular API Management backups so a corrupted policy push or an accidental deletion can be rolled back. POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/backup writes to a storage account container, and the matching restore endpoint reverses it on demand.
Back up API Management service 'contoso-apim' in resource group 'rg-prod' to storage account 'contosobackups' container 'apim-backups'
Pre-Provisioning Name and Region Checks
Before creating an API Management service, automation needs to confirm the chosen DNS name is globally unique. POST /subscriptions/{subscriptionId}/providers/Microsoft.ApiManagement/checkNameAvailability validates the name and surfaces the reason if it is taken, so deployment templates fail fast with a clear error.
Call POST /subscriptions/{subscriptionId}/providers/Microsoft.ApiManagement/checkNameAvailability with name 'contoso-apim' and report the result
Network Configuration Drift Resolution
When VNet integration changes (subnets, NSGs) outside an APIM update, the service can flag pending network reconfiguration. POST /service/{serviceName}/applynetworkconfigurationupdates re-applies the current configuration so the data plane and gateway re-converge with the underlying network state.
Apply queued network configuration updates to service 'contoso-apim' in resource group 'rg-prod' and poll until the operation succeeds
Agent-Driven APIM Inventory
An AI agent producing an Azure cost or compliance report can list every API Management instance in a subscription, fetch details, and flag SKUs or regions that violate policy. Through Jentic, the agent searches by intent and gets the right list/get operations with their schemas; the Azure OAuth token is held in the credential vault.
Search Jentic for 'list Azure API Management services', execute against subscription 1111-2222-3333-4444, and emit a CSV of name, region, and SKU
Key Endpoints
13 endpoints — jentic publishes the only available openapi specification for azure api management client, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/providers/Microsoft.ApiManagement/service
List API Management services in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service
List services in a resource group
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}
Get a service
POST
/subscriptions/{subscriptionId}/providers/Microsoft.ApiManagement/checkNameAvailability
Check service name availability
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/backup
Back up a service
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/applynetworkconfigurationupdates
Apply queued network configuration updates
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/getssotoken
Get an SSO token
GET
/subscriptions/{subscriptionId}/providers/Microsoft.ApiManagement/service
List API Management services in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service
List services in a resource group
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}
Get a service
POST
/subscriptions/{subscriptionId}/providers/Microsoft.ApiManagement/checkNameAvailability
Check service name availability
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/backup
Back up a service
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/applynetworkconfigurationupdates
Apply queued network configuration updates
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/getssotoken
Get an SSO token
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
ApiManagementClient
- Foundational (D-)43/100
99
Foundational Compliance56
Developer Experience & Jentic Compatibility20
AI-Readiness & Agent Experience94
Agent Usability35
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
20
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
76%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
4%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
35
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
35%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Azure API Management by hand means registering an Azure AD app, acquiring and refreshing OAuth 2.0 bearer tokens for management.azure.com, and polling the long-running backup and restore operations yourself. Through Jentic you install once, import Azure API Management from the API Directory, store the service principal credential once, and your agent calls it.
Permission scoping
Service instances are addressed by path parameters (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/...), so a rule can pin your agent to one subscription, resource group, and named service. You choose the operations it may call, so destructive ones like backup restore or applying network configuration updates are not included unless you add them.
Credential isolation
Your Azure AD service principal credential is stored once, encrypted, by your own Jentic One instance and exchanged for a short-lived bearer token at execution time. The secret never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'back up an Azure API Management service' or 'list API Management instances in a subscription', and Jentic returns the matching operation with its input schema so the agent supplies the storage account and service name without walking the Microsoft.ApiManagement path tree.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Azure API Management Client API through Jentic.
Why is there no official OpenAPI spec for Azure API Management Client?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Azure API Management Client 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 Azure API Management Client use?
The API uses Azure Active Directory OAuth 2.0 bearer tokens (the azure_auth scheme) on management.azure.com. Jentic holds the AAD app secret in your Jentic One instance and exchanges it for a short-lived bearer token per call.
Can I back up an API Management service with this API?
Yes. POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/backup takes the storage account, container, and blob name and writes a backup. The endpoint is asynchronous; poll the returned operation until it succeeds.
How do I check whether an APIM service name is available?
Call POST /subscriptions/{subscriptionId}/providers/Microsoft.ApiManagement/checkNameAvailability with the proposed name. The response indicates availability and includes a reason and message when the name is not allowed, so deployments can fail fast with a useful error.
What are the rate limits for this API?
Azure Resource Manager applies subscription-level throttling. Backup and restore endpoints are tighter because they trigger long-running operations. Honour HTTP 429 Retry-After values and avoid back-to-back backup calls on the same service.
How do I run a scheduled APIM backup through Jentic?
Run pip install jentic, then search Jentic with 'back up Azure API Management service'. Jentic returns the backup endpoint with its input schema. Load and execute with the storage account, container, and blob name; the OAuth token is resolved from the vault automatically.
Can I limit what my agent is allowed to do with the Microsoft Azure API Management Client API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. Since every service instance is addressed by path parameters (subscription, resource group, and service name), you can pin the agent to a single subscription, resource group, and named APIM service. You also choose exactly which operations it may call, so you can grant read-only actions like listing services or getting service details while leaving out destructive ones such as backup, restore, or applying network configuration updates.
GET STARTED