Microsoft Azure CdnManagementClient
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingoauth235 EndpointsREST
For Agents
Provision Azure CDN profiles and endpoints, manage custom domains and origins, and run purge, prefetch, start, and stop actions on the CDN.
Use for: I need to provision a new Azure CDN profile and endpoint, Purge a list of paths from my CDN endpoint after a deployment, Pre-load a set of URLs into the CDN cache before a campaign launches, Add a custom domain to my CDN endpoint and enable HTTPS
Not supported: Does not handle DNS zone records, WAF rule definitions, or origin storage provisioning — use for CDN profile, endpoint, custom domain, and origin management only.
Jentic publishes the only available OpenAPI specification for CdnManagementClient, keeping it validated and agent-ready. The Azure CDN management API administers CDN profiles, endpoints, custom domains, and origins through Azure Resource Manager. It exposes lifecycle operations plus the operational primitives content teams rely on — purge, prefetch, start, stop, custom HTTPS enable/disable, and SSO URI generation — so a CDN deployment can be fully managed from code.
Install Jentic One Beta
Connect the CdnManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CdnManagementClient, 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 CdnManagementClient API.
Provision Azure CDN profiles and endpoints scoped to a resource group
Add custom domains to a CDN endpoint and enable or disable custom HTTPS
Purge or pre-load content paths on a CDN endpoint to refresh cached assets
Start, stop, and restart endpoints to control whether they serve traffic
List supported optimization types and validate custom domain mappings before going live
Generate SSO URIs to deep-link into the CDN portal for a profile
Inspect resource usage and enforce profile name availability checks before creation
Use Cases
Patterns agents use CdnManagementClient API for, with concrete tasks.
★ Cache invalidation after deployment
Frontend teams call Endpoints_PurgeContent after each deployment to flush old assets from the CDN. The endpoint accepts an array of content paths, supports wildcard purges, and returns an operation handle that can be polled. This is the supported alternative to relying on cache TTL expiration after a release.
Call Endpoints_PurgeContent for the affected profile and endpoint with a list of paths from the deployment manifest
Custom domain with HTTPS
Marketing teams attach a vanity domain to a CDN endpoint with CustomDomains_Create, then call CustomDomains_EnableCustomHttps to provision a CDN-managed certificate. Validation can be checked first via Endpoints_ValidateCustomDomain so DNS misconfiguration is caught before the create call.
Call Endpoints_ValidateCustomDomain, then CustomDomains_Create, then CustomDomains_EnableCustomHttps with a CDN-managed certificate
Pre-warm CDN before campaign
Engineering teams call Endpoints_LoadContent the night before a high-traffic campaign to prime the CDN with the assets that will be requested. Combined with optimisation type lookup via Profiles_ListSupportedOptimizationTypes, this ensures the right delivery profile is in place before launch.
Call Endpoints_LoadContent with the list of campaign asset URLs ahead of launch
AI agent integration via Jentic
A site-reliability agent uses Jentic to orchestrate CDN operations during deployment workflows. The agent searches Jentic for 'purge an Azure CDN endpoint', loads the Endpoints_PurgeContent schema, and executes with the path list. Jentic mints AAD tokens against management.azure.com so credentials never reach the agent prompt.
Use Jentic search 'purge an Azure CDN endpoint' and execute Endpoints_PurgeContent with the deployment manifest paths
Key Endpoints
35 endpoints — jentic publishes the only available openapi specification for cdnmanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cdn/profiles/{profileName}
Create or update a CDN profile
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cdn/profiles/{profileName}/endpoints/{endpointName}
Create or update a CDN endpoint
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cdn/profiles/{profileName}/endpoints/{endpointName}/purge
Purge content paths from an endpoint
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cdn/profiles/{profileName}/endpoints/{endpointName}/load
Pre-load content paths into the CDN
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cdn/profiles/{profileName}/endpoints/{endpointName}/customDomains/{customDomainName}/enableCustomHttps
Enable HTTPS on a custom domain
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cdn/profiles/{profileName}/endpoints/{endpointName}/validateCustomDomain
Validate a custom domain before adding it
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cdn/profiles/{profileName}
Create or update a CDN profile
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cdn/profiles/{profileName}/endpoints/{endpointName}
Create or update a CDN endpoint
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cdn/profiles/{profileName}/endpoints/{endpointName}/purge
Purge content paths from an endpoint
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cdn/profiles/{profileName}/endpoints/{endpointName}/load
Pre-load content paths into the CDN
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cdn/profiles/{profileName}/endpoints/{endpointName}/customDomains/{customDomainName}/enableCustomHttps
Enable HTTPS on a custom domain
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cdn/profiles/{profileName}/endpoints/{endpointName}/validateCustomDomain
Validate a custom domain before adding it
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD OAuth 2.0 tokens are minted and rotated inside the Jentic vault. Agents receive scoped, short-lived tokens for management.azure.com — client secrets never enter agent context.
Intent-based discovery
Agents search Jentic by intent, e.g. 'purge an Azure CDN endpoint', and Jentic returns Endpoints_PurgeContent with its input schema so the agent calls the right endpoint without browsing ARM docs.
Time to first call
Direct integration: 2-3 days for AAD auth, ARM polling, and CDN async operation handling. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using CdnManagementClient API through Jentic.
Why is there no official OpenAPI spec for CdnManagementClient?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CdnManagementClient 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 CdnManagementClient API use?
The API uses Azure Active Directory OAuth 2.0 declared as azure_auth with the implicit flow against management.azure.com. Tokens are presented as Bearer headers. Through Jentic, the AAD client secret stays in the vault and the agent only ever sees scoped, short-lived tokens.
Can I purge multiple paths from a CDN endpoint in one call?
Yes. Endpoints_PurgeContent at /profiles/{profileName}/endpoints/{endpointName}/purge accepts a contentPaths array, including wildcards like /js/* or /images/*. The call returns an async operation handle that can be polled to confirm completion.
What are the rate limits for the CdnManagementClient API?
Azure Resource Manager applies subscription-level throttling, typically 12,000 read and 1,200 write requests per hour, surfaced via x-ms-ratelimit-remaining headers. CDN purge operations have additional per-day caps documented by Microsoft for cost control.
How do I purge a CDN endpoint through Jentic?
Run pip install jentic, then use the async client to search 'purge an Azure CDN endpoint', load Endpoints_PurgeContent, and execute with subscriptionId, resourceGroupName, profileName, endpointName, and a contentPaths array. Jentic returns the async operation handle for polling.
Can I use a CDN-managed certificate for a custom domain?
Yes. Call CustomDomains_EnableCustomHttps with a body indicating the CDN-managed certificate source. The API issues and binds the certificate, and the operation completes asynchronously — typically within minutes for already-validated domains.
GET STARTED