canonical: https://jentic.com/apis/ote-godaddy.com/certificates

# Ote Godaddy GoDaddy Certificates API

Manage SSL/TLS certificates through GoDaddy's certificate authority infrastructure. Order, validate, issue, reissue, renew, and revoke SSL certificates with support for domain validation workflows, callback webhooks, and email-based verification. The API handles the complete certificate lifecycle including CSR validation, CA approval workflows, and certificate bundle download.

## For AI agents

Order, manage, and renew SSL/TLS certificates with automated domain validation and CA approval workflows.

## Scope

Does not handle domain registration, DNS management, or web hosting - use for SSL/TLS certificate lifecycle management only.

## Capabilities

- Order SSL/TLS certificates with CSR submission and domain validation
- Track certificate status through polling or webhook callbacks
- Reissue certificates to add or remove domain names
- Renew expiring certificates within the validity window
- Download certificate bundles with intermediate CA chain
- Manage domain validation emails and resend verification requests

## Use cases

### Automated SSL Certificate Provisioning for Web Applications

Provision SSL/TLS certificates for web applications and APIs through automated workflows. The API handles CSR submission, domain validation via email or DNS, CA approval, and certificate issuance. Supports multi-domain certificates (SANs) and provides webhook callbacks for status updates, eliminating manual polling. Integration takes 1-2 days with callback handling.

Example prompt: Order an SSL certificate for example.com with SANs www.example.com and api.example.com, register a webhook callback, and download the certificate bundle once issued

### Certificate Lifecycle Management for SaaS Platforms

Manage SSL certificate renewals, reissues, and revocations for multi-tenant SaaS platforms hosting customer domains. Track certificate expiration dates, automatically trigger renewal workflows 60 days before expiry, and handle domain ownership changes through certificate reissue with updated SANs. The API supports unlimited reissues during certificate lifetime.

Example prompt: Check certificate expiration date for cert ID abc123, initiate renewal if within 60 days of expiry, and track renewal status via callback webhook

### Domain Validation Email Management

Handle domain validation workflows for SSL certificate orders by managing validation emails. Retrieve email history to confirm delivery, resend validation emails to alternate addresses if the original contact is unavailable, and track which validation steps are complete. Useful for complex domain ownership scenarios or when multiple stakeholders need to approve certificate requests.

Example prompt: Retrieve email history for certificate order xyz789, identify pending validation emails, and resend validation to admin@example.com

### AI Agent SSL Certificate Orchestration via Jentic

AI agents use Jentic to discover and execute SSL certificate operations without hardcoded API integration. Agents search by intent (e.g., 'order an SSL certificate'), Jentic returns the GoDaddy Certificates API with schema, and the agent submits the request with credentials managed by Jentic's your Jentic One instance. Eliminates manual certificate management workflows and reduces provisioning time from hours to minutes.

Example prompt: Search Jentic for 'order SSL certificate', load the GoDaddy Certificates API schema, and execute a certificate order with CSR for example.com using isolated credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/certificates` | Create a pending certificate order |
| POST | `/v1/certificates/validate` | Validate certificate order before submission |
| GET | `/v1/certificates/{certificateId}` | Retrieve certificate details and status |
| GET | `/v1/certificates/{certificateId}/download` | Download certificate bundle with CA chain |
| POST | `/v1/certificates/{certificateId}/renew` | Renew an expiring certificate |
| POST | `/v1/certificates/{certificateId}/reissue` | Reissue certificate with modified domains |
| PUT | `/v1/certificates/{certificateId}/callback` | Register webhook for status updates |
| GET | `/v1/certificates/{certificateId}/actions` | Retrieve all certificate lifecycle actions |

## Key resources

- **Certificates** — Create, retrieve, validate, cancel, reissue, renew, and download SSL/TLS certificates
- **Certificate Actions** — Retrieve stateful action history for certificate lifecycle events
- **Callbacks** — Register, retrieve, and unregister webhook callbacks for certificate status updates
- **Email History** — Retrieve and resend domain validation emails for certificate orders

## Why Jentic

- **Setup:** Wiring the GoDaddy Certificates API by hand means setting up the GoDaddy API key and secret pair, targeting the api.godaddy.com host, and managing your own retries across the SSL certificate lifecycle. Through Jentic you install once, import the GoDaddy Certificates API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Certificates API puts the certificate id in the URL path (`/v1/certificates/{certificateId}/...`), so a rule can pin your agent to one certificate: it can read status, download, and check actions for that certificate. You choose the operations it may call, so renew and reissue are not included unless you add them.
- **Credential handling:** Your GoDaddy API key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'request a new SSL certificate' or 'download an issued certificate', and Jentic returns the matching GoDaddy Certificates operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloudflare API** — CDN and DNS management API that can provision Cloudflare-managed SSL certificates
- **GoDaddy Domains API** — Manage domain registrations, DNS records, and domain transfers
- **GoDaddy Aftermarket API** — Buy, sell, and auction domain names in the GoDaddy aftermarket

## FAQ

### What authentication does the GoDaddy Certificates API use?

The GoDaddy Certificates API uses API key authentication passed in request headers. Jentic's your Jentic One instance stores your GoDaddy API key encrypted in the credential vault. Agents receive scoped access tokens - the raw API key never enters the agent's context. This isolation prevents credential leakage across tool calls.

### Can I order multi-domain SSL certificates with the GoDaddy Certificates API?

Yes, the API supports multi-domain SSL certificates through Subject Alternative Names (SANs). When creating a certificate order via POST `/v1/certificates`, include the common name and additional SANs in the request body. You can also add or remove domains through the reissue endpoint, which supports unlimited reissues during the certificate lifetime.

### What are the rate limits for the GoDaddy Certificates API?

Rate limit details are not specified in the OpenAPI specification. Contact GoDaddy's developer support for current rate limits and throttling policies. The API uses standard HTTP status codes (401, 403, 429) to indicate authentication and rate limit errors.

### How do I track certificate order status with the GoDaddy Certificates API?

The API provides two methods for tracking certificate status: polling via GET `/v1/certificates/{certificateId}/actions` to retrieve stateful action history, or webhook callbacks registered via PUT `/v1/certificates/{certificateId}/callback.` Webhooks eliminate the need for polling - GoDaddy POSTs status updates to your registered callback URL as the certificate progresses through validation, approval, and issuance.

### Can I renew SSL certificates before they expire with this API?

Yes, certificate renewal is available 60 days before expiration and up to 30 days after expiration. Use POST `/v1/certificates/{certificateId}/renew` with a new CSR and optionally modified SANs. The API extends the certificate validity period while maintaining the same certificate ID. New domains that don't share the base domain may require additional validation time.

### How do I resend domain validation emails if the original contact is unavailable?

Retrieve the email history for a certificate using GET `/v1/certificates/{certificateId}/email/history` to see which emails were sent. Resend a specific email to an alternate address using POST `/v1/certificates/{certificateId}/email/resend/{emailAddress}`, or resend all emails using POST `/v1/certificates/{certificateId}/email/{emailId}/resend.` This is useful when domain ownership contacts change or validation emails are not received.

### How do AI agents use the GoDaddy Certificates API through Jentic?

Install the Jentic MCP server in Claude Desktop or use the Python SDK with pip install jentic. Import with from jentic import Jentic, SearchRequest, LoadRequest, ExecutionRequest. Agents search for operations like order an SSL certificate, Jentic returns the GoDaddy Certificates API with the POST `/v1/certificates` endpoint schema, then the agent executes the request with credentials from the vault. Get started with Jentic One, the self-hosted execution layer.

### Can I limit what my agent is allowed to do with the GoDaddy Certificates API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. Since the API puts the certificate ID in the URL path (`/v1/certificates/{certificateId}/...`), you can pin an agent to a single certificate and grant only read-only operations, such as checking status, listing actions, and downloading the bundle. State-changing calls like renew and reissue stay off unless you explicitly add them.