/hackerone/leaderboard

POST /api/hackerone/leaderboard

Price: 5 credits

Get the HackerOne (hackerone.com) hacker leaderboard for a period and ranking type

How to use it

Get the HackerOne (hackerone.com) leaderboard of ranked hackers for a year/quarter. Choose a ranking type (highest reputation, high/critical reputation, OWASP Top 10, by country, by asset type, up-and-comers, most upvoted), engagement type (bounty/response) and individual vs business. Returns rank, previous_rank, username, reputation, signal and impact.

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 ranked entries to return (min: 1)
• key string — Leaderboard ranking type (default: "highest_reputation"; one of: "highest_reputation", "high_critical_reputation", "owasp_top_10", "country", "asset_types", "up_and_comers", "most_upvoted")
• year integer — Leaderboard year (default: 2026; min: 2013; max: 2027)
• quarter integer nullable — Leaderboard quarter (1-4); omit for full year (min: 1; max: 4)
• engagement_type string — Program engagement type: bounty (bbp) or response (vdp) (default: "bbp"; one of: "bbp", "vdp")
• user_type string — Rank individuals or businesses (default: "individual"; one of: "individual", "business")
• filter string nullable — Key-dependent filter value: OWASP category 'a1'-'a10' for OWASP_TOP_10, ISO country code (e.g. 'US') for COUNTRY, asset type (e.g. 'WEB_APP') for ASSET_TYPES.

Response

• @type string (default: "HackeroneLeaderboardEntry")
• rank integer nullable
• previous_rank integer nullable
• user_id string nullable
• username string required
• image string nullable
• reputation integer nullable
• signal number nullable
• impact number 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.