/hackerone/programs/search

POST /api/hackerone/programs/search

Price: 1 credit

Search the HackerOne (hackerone.com) program directory

How to use it

Search the HackerOne (hackerone.com) directory of public bug bounty / VDP programs. Filter by keyword, asset type and program features (offers bounties, IBB, high response efficiency, managed by HackerOne, offers retesting, collaboration). Sort by launch date or resolved reports. Returns name, handle, url, bounty ranges, resolved report count and launch date.

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 programs to return (min: 1)
• keyword string nullable — Search programs by name or handle
• sort string — Sort field (default: "launched_at"; one of: "launched_at", "resolved_reports")
• sort_direction string — Sort direction (default: "DESC"; one of: "DESC", "ASC")
• offers_bounties boolean nullable — Only programs that offer bounties
• ibb boolean nullable — Only Internet Bug Bounty programs
• high_response_efficiency boolean nullable — Only programs with high response efficiency
• managed_by_hackerone boolean nullable — Only programs managed by HackerOne
• offers_retesting boolean nullable — Only programs that offer retesting
• collaboration boolean nullable — Only programs that allow bounty splitting
• asset_type string nullable — Only programs with an in-scope asset of this type (one of: "CIDR", "URL", "APPLE_STORE_APP_ID", "TESTFLIGHT", "OTHER_IPA", "GOOGLE_PLAY_APP_ID", "OTHER_APK", "WINDOWS_APP_STORE_APP_ID", "SOURCE_CODE", "DOWNLOADABLE_EXECUTABLES", "SMART_CONTRACT", "WILDCARD", "IP_ADDRESS", "HARDWARE", "OTHER", "AI_MODEL", "API", "AWS_CLOUD_CONFIG", "AZURE_CLOUD_CONFIG")

Response

• @type string (default: "HackeroneDirectoryProgram")
• id string nullable
• name string required
• handle string required
• url string required
• image string nullable
• submission_state string nullable
• state string nullable
• triage_active boolean nullable
• publicly_visible_retesting boolean nullable
• allows_bounty_splitting boolean nullable
• launched_at string nullable
• currency string nullable
• base_bounty number nullable
• min_bounty number nullable
• average_bounty_lower_amount number nullable
• average_bounty_upper_amount number nullable
• resolved_report_count integer 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.