> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pulsedive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrate with D3 Security

> Use the D3 Pulsedive integration to check URL reputation against Pulsedive from your D3 playbooks and schedules.

[D3 Security](https://d3security.com/) is a security platform where teams run integration commands from playbooks and schedules.
The Pulsedive integration adds a URL reputation command to D3, so a playbook or a schedule can check a URL against Pulsedive.

This is an enrichment integration that queries the Pulsedive API on demand.
To import Pulsedive data in bulk instead, visit [Feed](https://docs.pulsedive.com/export/overview.md).

## Available Commands

These commands cover URL lookups and connection health, so a playbook can enrich a URL and you can confirm the connection still works:

* **Check URL Reputation**: Retrieves reputation details for the specified URLs.
* **Test Connection**: Performs a health check on the integration connection.

## Prerequisites

Before you connect D3 to Pulsedive, make sure you have the account and access the integration needs:

* A Pulsedive account and API key.
  D3 recommends these for programmatic access.
  Without a key, Pulsedive applies stricter rate limits."
* D3 ASOC version `12.7` or later, with permission to add integration connections.
* Outbound connectivity to `https://pulsedive.com` on port `443`.

## Connecting D3 to Pulsedive

D3 calls the Pulsedive API through an integration connection that holds your API key.
Once the connection is added and active, its commands are available to your playbooks and schedules.

**1. Find the integration**

Open the Pulsedive integration in D3, so you can add a connection to it.

1. In D3, select **Configuration** from the header menu.
2. Select the **Integration** icon from the sidebar menu.
3. Type `Pulsedive` in the search box, then select the integration.

**2. Add a connection**

Create a connection with your API key, so the integration's commands can authenticate with Pulsedive.

1. Select **+ Connection** in the **Connections** section.

2. Enter details for the connection:

   | Field Name | Description |
   | - | - |
   | **Connection Name** | Name for the connection. |
   | **Site** | Site that uses the connection. Select **Share to Internal Sites** to let all internal sites use it. |
   | **Recipient site for events from connections Shared to Internal Sites** | Internal site that deploys the connection. Appears only when **Site** is set to **Share to Internal Sites**. |
   | **Agent Name (Optional)** | Proxy agent that builds the connection. |
   | **Description (Optional)** | Description for the connection. |
   | **Tenant (Optional)** | Tenant sites that share the connection, when you configure it from a master tenant site. |
   | **Configure User Permissions** | Users who have access to the connection. |
   | **Active** | Select this to enable the connection. |
   | **System Reputation Check** | Reputation checks that D3 runs on its own for this connection. |
   | **Server URL** | Use `https://pulsedive.com`. |
   | **API Key** | Your Pulsedive API key. |
   | **Enable Password Vault** | Takes the stored credentials from your own password vault. |

   > [!NOTE]
   >
   > If you select a checkbox under **System Reputation Check**, D3 runs the matching reputation command on its own for every matching artifact from the site.
   > Each check is a request to the Pulsedive API, so account for it in your [API limits](https://docs.pulsedive.com/api/limits.md).

3. Select **Test Connection** and confirm that the test passes, then select **OK**.

4. Select **+ Add** to create the connection.

For the reference, visit D3's [Pulsedive integration page](https://docs.d3security.com/integration-docs/morpheus-integrations/pulsedive).

**3. Verify the connection**

Confirm that D3 can retrieve Pulsedive data before you build the command into a playbook.

1. Use D3's **Test Command** function to run **Check URL Reputation** against a URL Pulsedive already knows, such as one you can look up on [pulsedive.com](https://pulsedive.com).
   Enter the URL in **URLs** as a JSON array.
2. Confirm that the command succeeds and returns data for the URL.

   > [!TIP]
   >
   > If the command fails, open the **Error** tab in the test result to find the status code and message.
   > A status code of `429` means the request reached a Pulsedive rate limit, so check the [API limits](https://docs.pulsedive.com/api/limits.md) for your plan.

## Using Pulsedive Data in D3

Once the connection is active, add **Check URL Reputation** to a playbook or a schedule, so its output feeds your existing enrichment and response workflows.

If you schedule a **Connection Health Check** when you edit the connection, each check is also a request to the Pulsedive API.

To understand how Pulsedive scores an indicator, visit [Risk](https://docs.pulsedive.com/model/risk.md).
To review the request limits for your plan, visit [API limits](https://docs.pulsedive.com/api/limits.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.