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.