Microsoft Azure Azure API Management Client
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilityoauth213 EndpointsREST
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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: 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 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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure Active Directory OAuth 2.0 tokens are minted and rotated inside the Jentic vault (MAXsystem). Service principal client secrets stay encrypted; agents call Microsoft.ApiManagement with a short-lived scoped token only.
Intent-based discovery
Agents search by intent (e.g., 'back up Azure API Management service') and Jentic returns the matching APIM operation with its input schema, removing the need to traverse the Microsoft.ApiManagement path tree by hand.
Time to first call
Direct ARM integration: 1-3 days for AAD app registration, token acquisition, async polling, and storage account auth for backups. Through Jentic: under 1 hour — search, load schema, execute.
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 at https://app.jentic.com/sign-up.
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 the MAXsystem vault 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.
GET STARTED