> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/get-started/bring-in-findings/bug-bounty-programs/hackerone.md).
# HackerOne
Import vulnerability reports from your HackerOne program into Konvu.
Connect a HackerOne program to import vulnerability reports into Konvu automatically. Imported reports appear under **Triage > Vulnerability reports** for automated triage and reproduction.
## Prerequisites
* A HackerOne program
* Permission to create an API token for the program
## Setup steps
1. In HackerOne, open **Organization Settings > API Tokens** and create an API token.
2. In Konvu, open [**Integrations**](https://app.konvu.com/configuration/integrations) and select **HackerOne**.
3. Enter the connection details:
* **Display name**: A name that identifies this HackerOne connection, such as `Production`.
* **Token identifier**: Your HackerOne username when using a personal API token.
* **Token value**: The API token you created in HackerOne.
4. Click **Connect**.
Enter the HackerOne API token identifier and value, then click Connect
Konvu uses the credentials to read reports from the connected program. It does not write to HackerOne.
## Verify reports are flowing
After connecting, open **Triage > Vulnerability reports** in Konvu. Imported reports appear there with a link to the original HackerOne submission. New reports sync automatically.
If no reports appear, verify that the token is active and belongs to a user with access to the HackerOne program.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.konvu.com/konvu/get-started/bring-in-findings/bug-bounty-programs/hackerone.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
