Skip to main content
These endpoints turn your raw leak data into a security posture: a scored risk profile, leak statistics, trends over time, and a peer benchmark. All are read-only and scoped to your organization.

Risk score

get_organization_risk_score returns your current posture as nine weighted factors (score_a through score_i). Each factor carries a value, a plain-text message explaining it, and when it was last computed.
The factors run through score_i. Reading it: treat the *_message fields as a prioritized remediation list — the lowest-scoring factors are where your exposure concentrates. *_last_update tells you how fresh each factor is.

Leak statistics

get_organization_stats gives a quick sense of scale and skew:
Reading it: a median well below the average means a few large dumps are inflating your total — worth isolating those events rather than treating exposure as evenly spread.

Risk score over time

get_organization_risk_score_history returns a weekly series (set how far back with weeks — default 12, max 260). Each point carries two scores:
  • leak_risk_score — risk from your exposed and leaked data.
  • infra_risk_score — risk from your exposed infrastructure.
Reading it: plot both lines to see whether your posture is improving or degrading week over week, and which of the two dimensions is driving the move.

Leak volume over time

Two weekly series, both accepting the weeks parameter and returning the same { date, leak_count } shape:
Reading it: a spike in the weekly series flags a fresh breach or dump landing that week — your earliest signal to investigate. The total series shows how accumulated exposure is trending, which is the line you put in front of leadership.

Benchmark vs. peers

get_organization_benchmark_weekly_leak_count_history returns the peer average for each week:
Reading it: overlay this on your own weekly counts. A single leak number means little in isolation — sitting consistently above the peer average is the headline that justifies investment.

Competitors

The peer benchmark is built from competitors you choose, by domain. List themlist_organization_competitors returns a paginated set:
Add oneadd_organization_competitor, by domain:
Remove oneremove_organization_competitor with the competitor’s id from the list, passed as a query parameter: ?competitor_id=11. Reading it: each competitor’s leak_count is the same metric as your own, so you can answer “is our exposure normal for our sector?” — the context that turns a raw number into a decision.