whogothacked

API and MCP server

The same records as the site, for software: a read-only JSON API and an MCP server for AI assistants. No key is needed.

Before you build on it

  • Every response carries the incident’s tier and links to its source records. Please keep them with the data.
  • Some links are a list, not the record’s own page. The HHS breach portal has no page for each report, so every HHS record links its list. A Washington record links the notice’s own page on the Attorney General’s site, except a few from the state’s open data that match no notice in its directory, which link the directory. For a list link urlKind is list, url is that list, and findInList gives the name and date to look for. Do not present such a link as the record itself. A Washington notice letter is in documentUrls.
  • Each source record carries its own breach dates. An incident’s breachStart and breachEnd are one record’s, and are left out when its records disagree. A California notice lists separate days, never a range, so it gives them in breachDates instead, as does an incident that takes its dates: they are not a span. An incident’s lastReported is its latest date on record, which counts a Washington supplement letter by the letter’s own date. When a later supplement letter updated a Washington figure, affectedCount is the letter’s figure: supplements gives each letter’s date and the file it is in, and affectedListed the figure the notice page shows. When affectedListed equals affectedCount and no supplement gives a total, the notice’s letter gives another count and the figure stated is the notice page’s.
  • An incident’s firstReported is its first date on record and lastReported its latest, which can be later than firstReported (a later notice, catalog entry, filing or supplement letter). Neither is always a report or a filing: firstDateKind and lastDateKind say what each date is.
    • breach-notice: a state attorney general or HHS received or published a breach notice that day. A first date of this kind is "first reported".
    • sec-filing: the company filed a Form 8-K or 8-K/A with the SEC that day (its source record gives the form and items), and no notice is dated then. Say "disclosed to the SEC", not "first reported": an earlier filing this site does not hold may have disclosed the incident.
    • catalog: Have I Been Pwned added the entry to its catalog that day, and no other record is dated then. Say "added to the Have I Been Pwned catalog"; never call it a report or a filing.
    • organization-statement: the organization published its own statement that day, and no notice or SEC filing is dated then (no such record is published yet). Say "disclosed by the organization".
    • press-report: a named press report was published that day, and no notice, filing or statement is dated then (no such record is published yet). Say "first reported in the press".
    • other: no record on hand is dated that day, so nothing says what the date is. Say "first on record".
    • notice-supplement: lastDateKind only: the date of a supplement letter filed on a Washington notice, as the letter gives it (the record's supplements), not the day the Attorney General posted it.
    None of them is the date of the breach. More kinds can be added as sources are: accept a value you do not know, and word that date as other. An organization’s latestReported is the first date on record of the organization’s most recent incident (that incident’s firstReported), not its latest filing: an incident’s own lastReported can be later.
  • An SEC record gives its form in formType (8-K, or 8-K/A for an amendment). Every SEC record is under Item 1.05, except a Form 8-K filed under another item that a later Item 1.05 amendment amends: its items are in formItems.
  • A slug is never minted twice: a retired or taken-down slug is never given to another organization. When an organization is split, its slug stays with one of the parts and the other parts get new slugs. An incident id is never minted twice: a retired or taken-down id is never given to another incident. When an incident is split, its id stays with one of the parts and the other parts get new ids. A slug can be retired, for example when its organization is merged into another, or replaced after a rollback; an incident id, for example when its incident is merged into another, re-minted under its own organization, or replaced after a rollback. A retired one still answers, with the current record and redirectedFrom naming the one you asked for. One whose organization or incident was taken down is not found (the API answers 404, with no redirect). A slug that named a person who is not the organization (for example, an officer named in the filer's name) is withdrawn, not retired: it is not found (the API answers 404, with no redirect), and its organization goes on under another slug. An incident id made from a slug that named a person who is not the organization (for example, an officer named in the filer's name) is withdrawn, not retired: it is not found (the API answers 404, with no redirect), and its incident goes on under another id.
  • A miss means no record here. It never means an organization has not been breached, and your product should not say so.
  • Figures come with a scope and are never summed. Do not add them up.
  • Each IP address can make 120 requests a minute to the JSON API and, counted separately, 300 to the MCP server. Over that, the answer is HTTP 429 Too Many Requests: wait 60 seconds before trying again.
  • Using the API and MCP server means you accept the terms.
  • Descriptions from Have I Been Pwned are licensed CC BY 4.0 and need credit and a link when you show them.

How records are verified is on the methodology page. A plain-text summary for language models is at /llms.txt.

JSON API

Base address https://whogothacked.com. Every endpoint is a GET and returns JSON. CORS is open: every response from the site, errors included, carries Access-Control-Allow-Origin: *, so a web page on any site can call the API from the browser.

The one exception is a request over the rate limit. The edge refuses it with a 429 before it reaches the site, and that 429 carries no CORS headers and no Retry-After, so a browser reports a network or CORS error instead of the 429. When that happens, back off and try again after 60 seconds, when the window has passed.

GET/api/v1/search

Find organizations by name or domain. Returns each match with its incident count and `latestReported`, the first date on record of the organization's most recent incident (not its latest filing).

qstring, required
2 to 300 characters of an organization name or domain.
limitinteger, optional
1 to 100, default 20.

Example

curl "https://whogothacked.com/api/v1/search?q=conduent"

Open this example in the browser

GET/api/v1/orgs/{slug}

One organization with every incident on record and the source records behind each. A slug is never minted twice: a retired or taken-down slug is never given to another organization. When an organization is split, its slug stays with one of the parts and the other parts get new slugs. A slug can be retired, for example when its organization is merged into another, or replaced after a rollback; a retired slug still answers: the response is the current organization, with `redirectedFrom` naming the slug you asked for and `organization.slug` the one to keep. A slug whose organization was taken down answers 404, with no redirect. A slug that named a person who is not the organization (for example, an officer named in the filer's name) is withdrawn, not retired: it is not found (the API answers 404, with no redirect), and its organization goes on under another slug.

slugstring, required
The organization's slug, as returned by search.

Example

curl "https://whogothacked.com/api/v1/orgs/adobe"

Open this example in the browser

GET/api/v1/check

Answer 'is there anything on record for this organization: a breach notice, an 8-K disclosure or a catalog entry?'. `found` is true only for an exact domain or name; a looser match is offered under `candidates`, never as the answer. A miss means no record here, not that no breach happened.

domainstring, optional
A domain such as example.com, or a URL. Give this or `name`; if both are given the domain is tried first.
namestring, optional
An organization name; case, punctuation and legal forms such as Inc. are ignored. Give this or `domain`.

Example

curl "https://whogothacked.com/api/v1/check?domain=adobe.com"

Open this example in the browser

GET/api/v1/incidents/recent

Incidents newest first by the date they were first on record (`firstReported`): a filing's date, or the day Have I Been Pwned added an entry to its catalog. Each incident's `firstDateKind` says which.

sincedate, optional
Only incidents first on record on or after this date (YYYY-MM-DD).
untildate, optional
Only incidents first on record on or before this date (YYYY-MM-DD).
limitinteger, optional
1 to 500, default 50.
offsetinteger, optional
Rows to skip, default 0. Each response gives `nextOffset` while more remain.

Example

curl "https://whogothacked.com/api/v1/incidents/recent?since=2026-11-01&limit=25"

Open this example in the browser

GET/api/v1/incidents/{id}

One incident with its source records. An incident id is never minted twice: a retired or taken-down id is never given to another incident. When an incident is split, its id stays with one of the parts and the other parts get new ids. An id can be retired, for example when its incident is merged into another, re-minted under its own organization, or replaced after a rollback; a retired id still answers: the response is the current incident, with `redirectedFrom` naming the id you asked for and `incident.id` the one to keep. An id whose incident was taken down answers 404, with no redirect. An incident id made from a slug that named a person who is not the organization (for example, an officer named in the filer's name) is withdrawn, not retired: it is not found (the API answers 404, with no redirect), and its incident goes on under another id.

idstring, required
The incident id, as returned by the other endpoints.

Example

curl "https://whogothacked.com/api/v1/incidents/adobe-2013"

Open this example in the browser

GET/api/v1/meta

Record counts and when each source was last read successfully.

Takes no parameters.

Example

curl "https://whogothacked.com/api/v1/meta"

Open this example in the browser

MCP server

For AI assistants that speak the Model Context Protocol. The server uses the Streamable HTTP transport at one address:

Endpoint

https://whogothacked.com/mcp

Client configuration (JSON)

{
  "mcpServers": {
    "whogothacked": {
      "type": "http",
      "url": "https://whogothacked.com/mcp"
    }
  }
}

Claude Code

claude mcp add --transport http whogothacked https://whogothacked.com/mcp

Tools

search_breaches

Search the organizations on record, by name or domain.

querystring, required
Organization name or domain.
limitinteger, optional
1 to 50, default 10.

check_organization

Check one organization by exact domain or name and return its incidents with sources. A looser match comes back as candidates, never as the answer. A miss means no record here, not that no breach happened.

domainstring, optional
A domain such as example.com. Give this or `name`.
namestring, optional
An organization name. Give this or `domain`.

get_organization

Full record for one organization slug: every incident, figures, dates and source links. A slug can be retired, for example when its organization is merged into another, or replaced after a rollback; a retired slug returns the current organization, with `redirectedFrom` naming the slug asked for. A slug that named a person who is not the organization (for example, an officer named in the filer's name) is withdrawn, not retired: it is not found (the API answers 404, with no redirect), and its organization goes on under another slug.

slugstring, required
Organization slug from search_breaches.

get_incident

One incident with the source records that establish it. An id can be retired, for example when its incident is merged into another, re-minted under its own organization, or replaced after a rollback; a retired id returns the current incident, with `redirectedFrom` naming the id asked for. An incident id made from a slug that named a person who is not the organization (for example, an officer named in the filer's name) is withdrawn, not retired: it is not found (the API answers 404, with no redirect), and its incident goes on under another id.

idstring, required
Incident id.

recent_breaches

Incidents newest first by the date first on record, optionally within a date range.

sincedate, optional
YYYY-MM-DD, inclusive.
untildate, optional
YYYY-MM-DD, inclusive.
limitinteger, optional
1 to 100, default 25.

about_data

How records are verified, which sources are read, and when each was last updated.

Takes no parameters.