---
title: ThreatConnect Intelligence
slug: authentication-guides/threatconnect-intelligence
docTags: 
createdAt: 2026-09-30T22:07:12.858Z
---

This guide tells you how to authenticate the **ThreatConnect Intelligence** connector in Swimlane using **HMAC authentication**.

You will create a ThreatConnect API user, collect the Access ID and Secret Key, identify the appropriate API URL, and configure the connector in Swimlane.

## Prerequisites

### ThreatConnect Access Requirements

You must have ThreatConnect permissions to:

- Access **Organization Settings**.
- Create an API user for your organization.
- Assign the appropriate Organization role to the API user.

ThreatConnect requires an API user account for API access. The Swimlane connector authenticates using the API user's **Access ID** and **Secret Key** through HMAC authentication.

### Required Credentials

During setup, you will collect:

- URL
- Access Key
- Secret Key

These correspond to the required url, access\_key, and secret\_key fields in the Swimlane connector.

## ThreatConnect Setup

### Take the following steps to create an API user:

1. Log in to **ThreatConnect** using an account with permission to create API users.
2. From the top navigation bar, open **Settings** and select **Organization Settings**.
3. If applicable, select the organization for which you want to create the API user.
4. Click **Create API User**.
5. Enter the required user information.
6. Select the appropriate **Organization Role** based on the ThreatConnect data and operations the connector needs to access.
7. If **System Role** is available, select **Api User**.
8. Locate and copy the **Access ID** and **Secret Key** for the API user.
9. Securely save the **Secret Key** before closing the window.
10. Click **SAVE**.

:::hint{type="warning"}
ThreatConnect states that the Secret Key is not accessible after the API User Administration window is closed. Make sure you save it securely during API user creation.
:::

### Take the following steps to identify the API URL:

Use the API URL appropriate for your ThreatConnect deployment:

| **Deployment**                 | **API URL**                                 |
| ------------------------------ | ------------------------------------------- |
| ThreatConnect Public Cloud     | https\://app.threatconnect.com/api          |
| Dedicated Cloud or On-Premises | https\://\<your-threatconnect-instance>/api |

For example:

https\://companyabc.threatconnect.com/api

The Swimlane connector documentation specifies the /api URL for Public Cloud and Dedicated Cloud or On-Premises deployments.

## Connector configuration in Swimlane

1. Log in to Turbine.
2. From the left-hand navigation pane, click **ORCHESTRATION** and click **Assets**.
3. Asset homepage opens.
4. Click the plus icon to open the **Configure your Connector Asset** window.
5. Select **ThreatConnect Intelligence** from the Asset type list.
6. Fill in the Asset Settings and Asset Input as shown:

| Field       | Description                               | Required/Optional |
| ----------- | ----------------------------------------- | ----------------- |
| url         | ThreatConnect API URL                     | Required          |
| access\_key | Access ID for the ThreatConnect API user  | Required          |
| secret\_key | Secret Key for the ThreatConnect API user | Required          |
| verify\_ssl | Enable/Disable SSL Verification           | Optional          |
| http\_proxy | Optional proxy configuration              | Optional          |

The connector uses **ThreatConnect HMAC** authentication, and the URL, Access Key, and Secret Key are required.
Fields with \* marks are required.

7. Click **Create**.

::Image[]{src="https://api.archbee.com/api/optimize/n8uUzk0MM4uC57-zlHNtY/la7GxWJAIWJWQ4Y1GZ_T8_image.png" size="200" isUploading="false" width="2048" height="1065" darkWidth="2048" darkHeight="1065" showCaption="false"}

## Troubleshooting

If authentication fails:

- Verify that the **Access Key** and **Secret Key** belong to the same ThreatConnect API user.
- Verify that the API user has sufficient permissions for the actions you want to perform.
- Ensure that you entered the correct API URL for your ThreatConnect deployment.
- Verify that the API user has not been disabled.
- If you receive an authentication or unauthorized error, verify the Access ID and Secret Key. ThreatConnect identifies incorrect authentication credentials as a common cause of unauthorised API requests.
- If you receive a resource-not-found error, verify the ThreatConnect URL and API path.

:::hint{type="info"}
You have successfully authenticated the **ThreatConnect Intelligence** connector in Swimlane.
:::

## Sources

- **ThreatConnect - Managing User Accounts:**[ Managing User Accounts](https://knowledge.threatconnect.com/docs/managing-user-accounts?utm_source=chatgpt.com)
- **ThreatConnect API Documentation:**[ API Documentation](https://knowledge.threatconnect.com/docs/api-documentation?utm_source=chatgpt.com)
- **ThreatConnect - System Roles and Permissions:**[ System Roles and Permissions](https://knowledge.threatconnect.com/docs/threatconnect-system-roles-and-permissions?utm_source=chatgpt.com)