Microsoft Azure Certificates API Client
Browse all Azure APIsAgent-ready OpenAPI document · curated by JenticSecuritySecrets Managementoauth26 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage App Service certificate resources - list by subscription or resource group, get by name, and create, update, or delete certificates.
Use for: I need to upload a certificate so my App Service can bind it for SSL, List every App Service certificate in my subscription, Find all certificates in a single resource group, Retrieve a certificate by name to check its expiry date
Not supported: Does not bind certificates to App Service host names, purchase certificates, or expose private keys - use for App Service certificate resource management only.
Jentic publishes the only available OpenAPI specification for Certificates API Client, keeping it validated and agent-ready. The Azure App Service Certificates management API administers certificate resources stored under Microsoft.Web. It supports listing certificates by subscription or resource group, retrieving a specific certificate by name, and creating, updating, or deleting certificates that App Service apps consume for SSL binding.
Install Jentic One Beta
Connect the Certificates API Client to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Certificates API 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%2Fcertificates-api-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%2Fcertificates-api-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 Certificates API Client API.
List every App Service certificate in a subscription for inventory and audit
List App Service certificates within a single resource group
Retrieve a specific certificate by name to inspect its thumbprint and expiry
Create or update a certificate resource that App Service apps can bind to
Delete a certificate that is no longer required by any App Service binding
Patch certificate metadata such as tags or password without re-uploading
Use Cases
Patterns agents use Certificates API Client API for, with concrete tasks.
★ Upload an SSL certificate for App Service
Platform teams upload a PFX certificate as an Azure resource so any App Service in the same subscription can bind it. The PUT operation under /resourceGroups/{resourceGroupName}/providers/Microsoft.Web/certificates/{name} accepts the password-protected blob and returns the certificate resource with its thumbprint, ready for SSL binding.
Call PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/certificates/{name} with the PFX blob and password
Audit certificates by expiry
Compliance teams enumerate all certificates in a subscription via the list-by-subscription endpoint, inspect each thumbprint and expirationDate, and surface anything expiring within 30 days. This builds an automated reminder pipeline rather than relying on Azure Advisor or manual portal checks.
Call /subscriptions/{subscriptionId}/providers/Microsoft.Web/certificates, filter by expirationDate within 30 days, and emit alerts
Remove unused certificates
When an App Service binding is decommissioned, ops engineers list certificates in the resource group, identify the ones with no current bindings, and call DELETE on each. This keeps the inventory tidy and avoids paying storage for unused certificate resources.
List certificates by resource group, cross-reference against active bindings, and DELETE any unbound certificates
AI agent integration via Jentic
A platform agent uses Jentic to manage App Service certificates as part of automated SSL renewal flows. The agent searches Jentic for 'upload an Azure App Service certificate', loads the create operation schema, and executes with the PFX blob and password. Jentic mints AAD tokens against management.azure.com so the agent never holds a long-lived ARM token.
Through Jentic, search 'upload an Azure App Service certificate', load the create operation, and execute with the PFX bytes from a secret store
Key Endpoints
6 endpoints — jentic publishes the only available openapi specification for certificates api client, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Web/certificates
List certificates in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/certificates
List certificates in a resource group
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/certificates/{name}
Get a certificate by name
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/certificates/{name}
Create or update a certificate resource
PATCH
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/certificates/{name}
Update certificate metadata
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/certificates/{name}
Delete a certificate
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Web/certificates
List certificates in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/certificates
List certificates in a resource group
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/certificates/{name}
Get a certificate by name
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/certificates/{name}
Create or update a certificate resource
PATCH
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/certificates/{name}
Update certificate metadata
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/certificates/{name}
Delete a certificate
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Certificates API Client by hand means setting up Azure AD OAuth2 against management.azure.com and threading subscription, resource group, and certificate name ids through every Microsoft.Web certificate path yourself. Through Jentic you install once, import the Certificates API Client from the API Directory, store the Azure AD credential once, and your agent calls it.
Permission scoping
This API puts the certificate name in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/certificates/{name}), so a rule can pin your agent to one App Service certificate. You choose the operations it may call, so destructive ones like deleting a certificate or overwriting one with PUT 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 'upload an Azure App Service certificate' or 'list certificates in a resource group', and Jentic returns the matching Certificates operation with its input schema so the agent calls the right ARM path without browsing the Microsoft.Web reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Certificates API Client API through Jentic.
Why is there no official OpenAPI spec for Certificates API Client?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Certificates API 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 Certificates API Client 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 only short-lived scoped tokens reach the agent.
Can I bind a certificate to an App Service slot with this API?
No. This API manages certificate resources only. Binding a certificate to an App Service host name and slot is handled by the App Service / Web Apps API operations such as createOrUpdateHostNameBinding. Use this API to register the certificate, then bind it through the Web Apps API.
What are the rate limits for the Certificates API Client?
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. The certificate management endpoints fall within those limits.
How do I upload a PFX certificate through Jentic?
Run pip install jentic, then use the async client to search 'upload an Azure App Service certificate', load the create operation, and execute with subscriptionId, resourceGroupName, name, and a body containing the base64-encoded pfxBlob plus password. Jentic returns the certificate resource with thumbprint and expirationDate.
Does this API expose certificate private keys?
No. Reads return public certificate metadata such as thumbprint, subject name, issue date, and expiration date. The PFX blob and its password are accepted only on PUT/PATCH inputs and are not returned on GET responses.
Can I limit what my agent is allowed to do with the Certificates API Client?
Yes. Because you run Jentic One yourself, your own rules decide which certificate operations the agent can call and which Azure AD credential it uses. Since the certificate name sits in the URL path, you can pin the agent to a single App Service certificate. You choose the operations it may invoke, so destructive ones like deleting a certificate or overwriting one with PUT stay out of reach unless you explicitly add them.
GET STARTED