Microsoft Azure Azure API Management Client

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.