Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Cloud Infrastructure / Azure / CdnManagementClient
CdnManagementClient logo

Microsoft Azure CdnManagementClient

Browse all Azure APIs
44
AI ReadinessFoundational (D)44/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureNetworkingoauth235 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Jentic One on GithubView OpenAPI Document

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fcdn-management-client" | sh
2

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%2Fcdn-management-client" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

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.

C

CdnManagementClient

- Foundational (D)
44/100
70
Foundational Compliance
63
Developer Experience & Jentic Compatibility
22
AI-Readiness & Agent Experience
94
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
70

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
81%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

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.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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.

22

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
79%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

9%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

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.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the CdnManagementClient by hand means setting up Azure AD OAuth2 against management.azure.com, handling long-running operations for purge, prefetch, and endpoint start and stop, and threading profile, endpoint, and custom domain ids through every Microsoft.Cdn path yourself. Through Jentic you install once, import the CdnManagementClient from the API Directory, store the Azure AD credential once, and your agent calls it.

Permission scoping

This API puts the profile, endpoint, and custom domain ids in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cdn/profiles/{profileName}/endpoints/{endpointName}), so a rule can pin your agent to one CDN profile and its endpoints. You choose the operations it may call, so ones like purging cached content or stopping an endpoint are not included unless you add them.

Credential isolation

Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'purge an Azure CDN endpoint' or 'add a custom domain', and Jentic returns the matching Endpoints or CustomDomains operation with its input schema so the agent calls the right ARM path without browsing the Microsoft.Cdn reference.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure CDN Web Application Firewall Management

→

WAF policies attached to CDN endpoints for filtering malicious requests.

Use the WAF management API to define firewall policies; use this CDN management API to provision the underlying endpoints.

Complementary

Azure Web Application Firewall Management

→

General WAF management for Application Gateway and Front Door deployments.

Choose this for non-CDN WAF; choose CDN Management for the CDN profile itself.

Complementary

Azure Storage Management

→

Provisions blob storage commonly fronted by an Azure CDN endpoint.

Use Storage Management to provision the origin; use CDN Management to put a CDN in front of it.

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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Microsoft Azure CDN Management API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which operations and credentials your agent may use. This API carries the profile, endpoint, and custom domain ids in the URL path, so a rule can pin your agent to a single CDN profile and its endpoints. You choose exactly which operations it may call, so sensitive ones like Endpoints_PurgeContent or stopping an endpoint stay off limits unless you add them.

GET STARTED

Start building with CdnManagementClient API

Explore with Jentic One
View OpenAPI Document