Certificates API Client

Name: Certificates API Client API
Brand: Certificates API Client
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSecuritySecrets Managementoauth26 EndpointsREST

For Agents

Manage App Service certificate resources — list by subscription or resource group, get by name, and create, update, or delete certificates.

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.

Install Jentic One Beta (Self-Hosted)

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 | sh

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 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 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

GET STARTED

Start building with Certificates API Client API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Certificates API Client, keeping it validated and agent-ready.

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.

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

Why though 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. 'upload an Azure App Service certificate', and Jentic returns the create operation with its input schema so the agent calls the right endpoint without browsing ARM docs.

Time to first call

Direct integration: 1-2 days for AAD auth, ARM polling, and PFX handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure App Service Certificate Orders

Handles the purchase and renewal of App Service certificates that this API manages as resources.

Use Certificate Orders to buy or renew; use this API to manage the resulting certificate resource.

Complementary

Certificate Registration Provider

Discovery surface for the certificate registration resource provider used during purchase flows.

Use this for capability discovery; use Certificates API Client for actual resource management.

Alternative

Azure Key Vault Management

Manages certificates as Key Vault secrets rather than App Service certificate resources.

Use Key Vault for general-purpose certificate storage; use this API specifically for App Service domain SSL bindings.

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 at https://app.jentic.com/sign-up.

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.