/hackerone/reports/search

POST /api/hackerone/reports/search

Price: 5 credits

Search disclosed HackerOne (hackerone.com) vulnerability reports (hacktivity feed)

How to use it

Search the HackerOne (hackerone.com) hacktivity feed of disclosed vulnerability reports. Filter by keyword, reporter, program, severity, weakness (CWE), CVE, report state, reward range, disclosure date range, and collaboration. Returns report id, title, url, severity, CWE, CVE ids, awarded amount, votes, reporter, program, and an AI summary.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of reports to return (min: 1; max: 10000)
• keyword string nullable — Full-text search over report titles
• reporter string nullable — Filter by reporter username
• program string nullable — Filter by program handle
• severity array nullable — Filter by report severity rating (one of: "none", "low", "medium", "high", "critical")
• cwe string nullable — Filter by weakness (CWE) name, e.g. 'Cross-Site Scripting (XSS)'
• cve string nullable — Filter by CVE id, e.g. 'CVE-2026-50741'
• state string nullable — Filter by report state (one of: "resolved", "triaged", "informative", "not-applicable", "duplicate", "new", "spam")
• min_reward number nullable — Minimum total awarded bounty amount (min: 0)
• max_reward number nullable — Maximum total awarded bounty amount (min: 0)
• collaboration boolean nullable — Only reports with multiple collaborators
• disclosed boolean nullable — Filter by public disclosure state
• disclosed_after string nullable — Only reports disclosed on/after this date (YYYY-MM-DD)
• disclosed_before string nullable — Only reports disclosed on/before this date (YYYY-MM-DD)
• sort string — Sort field (default: "latest_disclosable_activity_at"; one of: "latest_disclosable_activity_at", "disclosed_at", "total_awarded_amount", "votes")
• sort_direction string — Sort direction (default: "DESC"; one of: "DESC", "ASC")

Response

• @type string (default: "HackeroneReport")
• id string nullable
• url string nullable
• state string nullable
• severity string nullable
• cwe string nullable
• cve_ids array (default: [])
• summary string nullable
• vote_count integer nullable
• awarded_amount number nullable
• disclosed boolean nullable
• disclosed_at string nullable
• submitted_at string nullable
• latest_activity_at string nullable
• latest_disclosable_action string nullable
• has_collaboration boolean nullable
• reporter object nullable
  • @type string (default: "HackeroneReportUser")
  • username string required
  • name string nullable
• team object nullable
  • @type string (default: "HackeroneReportTeam")
  • handle string required
  • name string nullable
  • url string nullable
  • image string nullable
• collaborators array (default: [])
  • @type string (default: "HackeroneReportUser")
  • username string required
  • name string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.