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 / Security / Google / Certificate Manager API
Certificate Manager API logo

Google Certificate Manager API

Browse all Google APIs
40
AI ReadinessNon-Ready (F)40/100
See full scorecard
Official vendor OpenAPI document · agent-readySecuritySecrets Managementoauth218 EndpointsREST

For Agents

Provision and rotate TLS certificates, manage certificate maps and trust configs, and operate Google-managed or self-managed certs across Google Cloud load balancers.

Use for: Provision a Google-managed TLS certificate for example.com, Upload a self-managed certificate and private key, List all certificates in a Google Cloud project location, Create a certificate map entry binding a hostname to a certificate

Not supported: Does not issue private CAs, manage DNS records, or terminate TLS at the application layer - use for managing TLS certificates and trust configs on Google Cloud load balancers only.

Google Cloud Certificate Manager API provisions, stores, and deploys TLS certificates and private trust configurations across Google Cloud load balancers and edge services. It supports Google-managed and self-managed certificates, certificate maps that route SNI-based hostnames to specific certificates, certificate issuance configurations for Certificate Authority Service, and trust configs that pin private CAs. Operations teams use it to automate certificate lifecycle and avoid manual rotation across global load balancer fleets.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Certificate Manager API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Certificate Manager API, 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%2Fgoogleapis.com%2Fcertificatemanager" | 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%2Fgoogleapis.com%2Fcertificatemanager" | 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 Certificate Manager API.

Provision Google-managed TLS certificates that auto-renew before expiry

Upload and rotate self-managed TLS certificates with their private keys

Build certificate maps that bind hostnames to specific certificates via SNI

Configure certificate issuance configs that source certs from a Certificate Authority Service CA pool

Define trust configs that pin private root and intermediate CAs for mTLS workloads

Track long-running operations and cancel them mid-flight when needed

Use Cases

Patterns agents use Certificate Manager API for, with concrete tasks.

★ Automated TLS Rotation for Global Load Balancers

Platform teams replace manual certificate uploads with Google-managed certificates that auto-renew, then attach them to global external HTTPS load balancers via certificate maps. The API orchestrates provisioning, validation, and binding so that hostnames behind a single load balancer can each carry their own certificate. Rotation requires no traffic switch and no downtime.

Create a Google-managed Certificate resource for example.com via POST /v1/{parent}/certificates and bind it through a certificate map entry.

mTLS with Pinned Private CAs

Security engineers configure trust configs that pin specific private root and intermediate CAs, then attach them to load balancers that require client certificates. This enables zero-trust mutual TLS for service-to-service traffic without trusting the public web PKI. Trust configs are versioned and updated atomically.

Create a TrustConfig under /v1/{parent}/trustConfigs containing the customer's private root CA PEM and intermediate CA chain.

Multi-Hostname SNI Routing

SaaS providers serve hundreds of customer domains behind a single global IP using certificate maps and certificate map entries. Each entry binds an SNI hostname to a specific certificate, and entries can be added or removed without recreating the map. Onboarding a new customer domain is a single POST.

Create a certificate map entry binding hostname customer1.app.example.com to a previously provisioned certificate via POST /v1/{parent}/certificateMapEntries.

AI Agent Certificate Operator via Jentic

An AI agent through Jentic responds to a user request to issue a certificate for a new hostname, runs the provisioning operation, polls until status is ACTIVE, and binds it to the relevant certificate map. Jentic isolates the Google Cloud OAuth credentials so the agent never sees the service account key directly. The whole flow runs through three Jentic calls.

Through Jentic, search certificatemanager_create_certificate, load schema, and execute with project, location, and a managed certificate config for hostname app.example.com.

Key Endpoints

18 endpoints — google cloud certificate manager api provisions, stores, and deploys tls certificates and private trust configurations across google cloud load balancers and edge services.

METHOD

PATH

DESCRIPTION

POST

/v1/{+parent}/certificates

Create a managed or self-managed TLS certificate

GET

/v1/{+parent}/certificates

List certificates in a location

POST

/v1/{+parent}/certificateMaps

Create a certificate map for SNI routing

POST

/v1/{+parent}/certificateMapEntries

Bind a hostname to a certificate within a map

POST

/v1/{+parent}/trustConfigs

Create a trust config pinning private CAs

POST

/v1/{+name}:cancel

Cancel a long-running operation

POST

/v1/{+parent}/certificates

Create a managed or self-managed TLS certificate

GET

/v1/{+parent}/certificates

List certificates in a location

POST

/v1/{+parent}/certificateMaps

Create a certificate map for SNI routing

POST

/v1/{+parent}/certificateMapEntries

Bind a hostname to a certificate within a map

POST

/v1/{+parent}/trustConfigs

Create a trust config pinning private CAs

POST

/v1/{+name}:cancel

Cancel a long-running operation

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

Certificate Manager API

- Non-Ready (F)
40/100
69
Foundational Compliance
56
Developer Experience & Jentic Compatibility
18
AI-Readiness & Agent Experience
94
Agent Usability
63
Security
53
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
69

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 4
75%

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.

56

Developer Experience & Jentic Compatibility

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

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

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.

18

AI-Readiness & Agent Experience

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

Grade: FSignals: 4
70%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

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.

63

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
62%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

53

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C-Signals: 1
53%

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 Certificate Manager API by hand means setting up Google Cloud service account auth, minting scoped access tokens, and driving certificate, map, and trust-config calls through the long-running operations model yourself. Through Jentic you install once, import the Certificate Manager API from the API Directory, store the service account credential once, and your agent calls it.

Permission scoping

The API puts the project and resource in the URL path (/v1/{+parent}/certificates, /v1/{+name}:cancel), so a rule can pin your agent to one project: it can create certificates, maps, and trust configs there and nowhere else. You choose the operations it may call, so canceling or deleting a resource is not included unless you add it.

Credential isolation

Your Google Cloud service account key is stored once, encrypted, by your own Jentic One instance and injected at execution time. The agent receives only short-lived scoped access tokens and the service account JSON never enters its prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'provision a TLS certificate for example.com on Google Cloud', and Jentic returns the certificates create operation with its full input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Cloud KMS API

→

Manage cryptographic keys that may sign or wrap certificate private keys.

Use Cloud KMS to protect signing keys; use Certificate Manager to deploy the resulting certificates to load balancers.

Complementary

Cloud DNS API

→

Manage the DNS records that prove domain ownership for managed certificate issuance.

Use Cloud DNS to create the validation CNAME or TXT records that Certificate Manager checks before issuing a managed certificate.

Complementary

Google Cloud IAM API

→

Grant and revoke roles such as roles/certificatemanager.editor on certificate resources.

Use IAM to authorise principals before delegating Certificate Manager operations to them.

FAQs

Specific to using Certificate Manager API through Jentic.

What authentication does the Certificate Manager API use?

It requires OAuth 2.0 with the cloud-platform scope, typically via a Google Cloud service account key. Through Jentic, that service account credential lives in your Jentic One instance and the agent receives only short-lived access tokens scoped to the request.

Can I provision a Google-managed TLS certificate via the API?

Yes. POST a Certificate resource to /v1/{parent}/certificates with managed.domains set to the hostnames to cover. The provisioning is asynchronous; poll the returned operation under /v1/{+name}/operations until done is true and the certificate state is ACTIVE.

What are the rate limits for the Certificate Manager API?

Google Cloud applies per-project per-minute quotas (typically 60 write operations per minute and higher read quotas). Long-running operations such as managed certificate issuance can take several minutes to reach ACTIVE due to domain validation, not API throttling.

How do I create a certificate map entry through Jentic?

Use the Jentic search query "create a certificate map entry" to discover the certificateMaps.certificateMapEntries.create operation, load its schema, then execute it with the parent map, the hostname, and the certificate resource name. Run pip install jentic to get started.

Does the Certificate Manager API support self-managed certificates?

Yes. Provide selfManaged.pemCertificate and selfManaged.pemPrivateKey when creating a Certificate resource. Self-managed certificates do not auto-renew - the caller must rotate them by patching or replacing the resource before expiry.

Is the Certificate Manager API free?

API calls themselves are free. Google Cloud charges for active certificates and trust configs based on the load balancer pricing tier they are attached to. See the Google Cloud Certificate Manager pricing page for current rates.

Can I limit what my agent is allowed to do with the Google Cloud Certificate Manager API?

Yes. Because you self-host Jentic One, your own rules decide which Certificate Manager operations and credentials the agent may use. Since the API puts the project and resource in the URL path (for example /v1/{+parent}/certificates and /v1/{+name}:cancel), you can pin the agent to a single project and allow only the operations you choose, such as creating certificates, certificate maps, and trust configs. Destructive calls like canceling a long-running operation or deleting a certificate stay excluded unless you explicitly add them.

GET STARTED

Start building with Certificate Manager API

Explore with Jentic One
View OpenAPI Document