Cotool + HackerOne
Connect HackerOne to Cotool so new reports arrive as alerts and agents validate them against your code and logs, comment, change state, and close reports.
The short answer
Cotool's HackerOne connector turns incoming reports into alerts through webhook-triggered intake for vulnerability response workflows, and agents can comment on, change the state of, and close HackerOne reports.[1]
How it connects: Cotool calls the HackerOne Customer API. HackerOne uses HTTP Basic authentication with an API token's identifier as the username and its value as the password.[2][6]
What Cotool uses from HackerOne
Response actions
These change state in HackerOne, so they are the steps teams usually gate behind approval.
Detections, hunts, and triage
Setup and permissions
An Admin user generates an API token from the organization's settings page. The token can act only on programs and teams the API user is part of.[6][7]
| Permission | Access | Why |
|---|---|---|
| API token (read)Read reports for programs the API user belongs to.[6][7] | Read | Read reports for programs the API user belongs to.[6][7] |
| API token (write)Comment and change report state. Plans with read-only API access reject writes with 403.[6] | Write | Comment and change report state. Plans with read-only API access reject writes with 403.[6] |
- API users cannot be assigned to reports; only users and groups in the program can.[7]
How Cotool works with HackerOne
- Cotool added the HackerOne connector in release 0.57.0 and report comments, state changes, and closing in release 0.73.0.[1]
FAQ
- Does every HackerOne plan allow write access?
- No. HackerOne returns 403 for writes when the organization's plan only includes read-only API access.[6]
Sources
- Changelog (Cotool docs) · accessed November 16, 2026
- Integrations (Cotool) · accessed November 16, 2026
- Respond to every signal (Cotool Respond) · accessed November 16, 2026
- GitHub integration (Cotool docs) · accessed November 16, 2026
- Jira integration (Cotool docs) · accessed November 16, 2026
- Getting started (HackerOne API) · accessed November 16, 2026
- Customer resources (HackerOne API) · accessed November 16, 2026
