--- title: "How to integrate with a GoDaddy CA" slug: "clm-integrate-godaddy-ca" updated: 2026-11-06T13:52:54Z published: 2026-11-06T13:52:54Z canonical: "docs.senhasegura.io/clm-integrate-godaddy-ca" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.senhasegura.io/llms.txt > Use this file to discover all available pages before exploring further. # How to integrate with a GoDaddy CA This document provides information on how to integrate with a GoDaddy certificate authority. For more information about the GoDaddy certificate authority fields, see [Certificate authorities](/v4-2/docs/certificate-manager-reference-supported-cas#godaddy). ## Integrate with a GoDaddy CA 1. On Segura™, in the navigation bar, hover over the **Products menu** and select **Certificate Manager**. 2. In the side menu, select **Management** > **Authorities** > **Certificate authorities**. 3. In the top right corner, click **Add**, and select **GoDaddy**. 4. In the **Name *** field, enter a name to identify the CA. 5. Select the button **Status** to activate or deactivate the CA. 6. In the **Key** field, enter GoDaddy’s API key. 7. In the **Secret** field, enter GoDaddy's API secret. 8. Click **Save**. ## Supported certificate products When you sign a request with a GoDaddy CA, you select the certificate product in the **Product** field of the **GoDaddy** tab, and Segura® sends that product to GoDaddy. The field comes pre-selected based on the request's validation type and domain type. For more information, see [How to sign a request](/v4-2/docs/certificates-flow-how-to-sign-request). Only domain-validated (DV) products are available: | Product | Use | | --- | --- | | **DV SSL** | A single domain. | | **DV Wildcard SSL** | A wildcard domain, such as `*.example.com`. | | **DV UCC/SAN SSL** | Multiple names (common name and SANs). Segura® orders the smallest bundle that fits the names, from 5 up to 100 names. | For renewal requests, the **GoDaddy** tab shows the **Period** field instead of **Product**. ### Product compatibility Segura® rejects the request, with a message that explains the reason, if the product does not fit the request's names: - The request has more than one name (common name and SANs), but the product is not a multi-domain product. - The request has more names than the product supports. - The product is a wildcard product, but the request has no wildcard name. - The request has a wildcard name, but the product is not a wildcard product. ### Reissue A reissue request keeps the product of the original order. If GoDaddy rejects the reissue, the reason appears on the [Validation guidelines](/v4-2/docs/certificate-manager-reference-certificate-requests#validation-guidelines-screen) screen.