---
title: Hackerone
slug: connectors/hackerone
docTags: 
createdAt: 2026-06-09T16:30:04.828Z
---

HackerOne is a vulnerability coordination and bug bounty platform that enables organizations to connect with a vast community of cybersecurity researchers to identify and resolve security vulnerabilities.

HackerOne is a leading security platform that specializes in hacker-powered security through bug bounty programs and vulnerability disclosure. The HackerOne connector for Swimlane Turbine enables users to automate the retrieval of detailed analytics data from HackerOne, providing insights into vulnerability trends, hacker activity, and program effectiveness within specified timeframes and intervals. By integrating with HackerOne, Swimlane Turbine users can streamline their vulnerability management processes, enhance their security posture by leveraging real-time data, and make informed decisions based on comprehensive security metrics. This connector simplifies the process of fetching and analyzing security data, allowing users to focus on strategic response and proactive defense.

### Limitations

None to date.

### Supported Versions

This HackerOne connector uses the latest Version API.

## Configuration

### Prerequisites

To utilize the HackerOne connector within Swimlane Turbine, ensure you have the following prerequisites:

- HTTP Basic Authentication with the following parameters:
  - URL: The endpoint URL for the HackerOne API.
  - Username: Your HackerOne account username.
  - API Key: A valid API key generated from your HackerOne account for authentication purposes.

## Authentication Methods

## HTTP Basic Authentication

The HackerOne connector uses the HTTP Basic authentication method to connect to the HackerOne API.

To set up HTTP Basic Authentication, you need the following parameters:

**Username:** The API Token Identifier used as username for authentication.
**Password:** The API Token Value used as the password for authentication.
**URL:** The base URL of the HackerOne API.

## Capabilities

This HackerOne connector provides the following capabilities:

- Query Analytics

### Query Analytics

HackerOne's documentation for this action can be found [here](https://api.hackerone.com/use-cases/#program-analytics).

## Additional Documentation

- [Hackerone Connector Documentation](https://docs.swimlane.com/connectors/hackerone)
- [Hackerone API Documentation](https://api.hackerone.com/)

# Configurations

## HackerOne Basic Auth

Authenticates using username and password.

### Configuration Parameters

| **Parameter** | **Description**                                               | **Type** | **Required** |
| ------------- | ------------------------------------------------------------- | -------- | ------------ |
| url           | A URL to the target host.                                     | string   | Required     |
| username      | The API Token Identifier used as username for authentication. | string   | Required     |
| password      | The API Token Value used as the password for authentication.  | string   | Required     |
| verify\_ssl   | Verify SSL certificate                                        | boolean  | Optional     |
| http\_proxy   | A proxy to route requests through.                            | string   | Optional     |

# Actions

## Query Analytics

Retrieve analytics data for a specified key within a given time range and interval from HackerOne.

### Endpoint

- **URL:** `v1/analytics`
- **Method:** `GET`

### Input

| **Argument Name**            | **Type** | **Required** | **Description**                                                                                                        |
| ---------------------------- | -------- | ------------ | ---------------------------------------------------------------------------------------------------------------------- |
| `parameters.key`             | string   | Required     | Filter by the query key you want to fetch data for.                                                                    |
| `parameters.start_at`        | string   | Required     | The start date of the query as a string, inclusive. Format YYYY-MM-DD.                                                 |
| `parameters.end_at`          | string   | Required     | The end date of the query as a string, exclusive. Format YYYY-MM-DD.                                                   |
| `parameters.interval`        | string   | Required     | The interval to use for the input date range. Valid intervals are month, quarter, or year.                             |
| `parameters.team_id`         | string   | Optional     | Filter by a team/program ID. If no team\_id is provided, then data will be for all teams/programs in the organization. |
| `parameters.organization_id` | string   | Optional     | Filter by an organization ID.                                                                                          |

### Input Example

`{"parameters":{"key":"string","start_at":"string","end_at":"string","interval":"string","team_id":"string","organization_id":"string"}}`

### Output

| **Parameter**   | **Type** | **Description**                  |
| --------------- | -------- | -------------------------------- |
| `status_code`   | number   | HTTP status code of the response |
| `reason`        | string   | Response reason phrase           |
| `data`          | array    | Response data                    |
| `data.keys`     | array    | Response data                    |
| `data.values`   | array    | Response data                    |
| `data.values.0` | string   | Response data                    |
| `data.values.1` | string   | Response data                    |

### Output Example

`{"status_code":200,"reason":"OK","json_body":{"data":[{}]}}`

# Response Headers

| **Header**   | **Description**                                       | **Example**                   |
| ------------ | ----------------------------------------------------- | ----------------------------- |
| Content-Type | The media type of the resource                        | application/json              |
| Date         | The date and time at which the message was originated | Thu, 01 Jan 2024 00:00:00 GMT |