Skip to main content
Skip table of contents

GoDaddy

GoDaddy provides domain registration and web hosting along with tools to build sites, email hosting, and marketing tools

Requirements

To use the GoDaddy Connector in Lucidum:

  1. Before configuring the GoDaddy connector in Lucidum, you must first define an API Key and API Secret in GoDaddy. Lucidum will use the API key and API secret to access the GoDaddy API.

  2. You can then configure the GoDaddy connector in Lucidum and start ingesting data from GoDaddy.

Prerequisite: Defining an API Key and API Secret

  1. Login to GoDaddy (https://api.godaddy.com) with the account you want to use with the Lucidum connector.

  2. Select API Keys.

  3. Select Create New API Key.

  4. In the Create New API modal window, enter:

    • Name. Enter Lucidum.

    • Environment. Select Production.

  5. Copy the API Key and the API Secret.

Configuring the GoDaddy Connector

To configure Lucidum to ingest data from GoDaddy:

  1. Log in to Lucidum.

  2. In the left pane, click Connector.

  3. In the Connector page, click Add Connector.

  4. Scroll until you find the Connector for GoDaddy. Click Connect. The Settings page appears.

  5. In the Settings page, enter the following

    • URL. The URL for the GoDaddy API. For example, https://api.godaddy.com/.

    • API Key. The API key associated with an account that has read access to API data. You created and copied this value in the previous section.

    • API Secret. The API secret associated with an account that has read access to API data. You created and copied this value in the previous section.

  6. To test the configuration, click Test.

    • If the connector is configured correctly, Lucidum displays a list of services that are accessible with the connector.

    • If the connector is not configured correctly, Lucidum displays an error message.

API Documentation

API v1 and API v2

https://developer.godaddy.com/doc

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.