POST /api/hackerone/hackers
Price: 1 credit
Get a HackerOne (hackerone.com) hacker profile by username
Get a HackerOne (hackerone.com) hacker (security researcher) profile by username (or profile URL). Returns name, bio, location, country, website, social handles, cleared/verified flags, reputation, rank, resolved report count, thanks count, submission streak, badges and reviews.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)username string required — Hacker username ('d0xing') or profile URL ('https://hackerone.com/d0xing'). (examples: "d0xing", "https://hackerone.com/d0xing"; minLength: 1)@type string (default: "HackeroneHacker")id string nullableusername string requiredname string nullableintro string nullablebio string nullablelocation string nullablecountry string nullablewebsite string nullableurl string requiredimage string nullablecreated_at string nullablebugcrowd_handle string nullablecobalt_handle string nullablehack_the_box_handle string nullablegithub_handle string nullablegitlab_handle string nullablelinkedin_handle string nullabletwitter_handle string nullablecleared boolean nullableverified boolean nullableopen_for_employment boolean nullableis_company boolean nullablereputation integer nullablerank integer nullableresolved_report_count integer nullablethanks_count integer nullablecompleted_pentest_count integer nullablestreak object nullable@type string (default: "HackerStreak")length integer nullablestart_date string nullableend_date string nullablebadges array (default: [])@type string (default: "HackerBadge")name string requiredimage string nullableawarded_at string nullablereviews array (default: [])@type string (default: "HackerReview")text string nullableteam_handle string nullableteam_name string nullable422 — 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 — Hacker not found 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.