POST /api/haveibeenpwned/passwords
Price: 5 credits
Check whether a password has appeared in known data breaches (Pwned Passwords)
Check a password against the Pwned Passwords corpus of previously breached passwords. Provide either a plaintext password or a pre-computed SHA-1 / NTLM hash, plus the hashing mode. Returns the full hash, whether it was found in a breach, and how many times it has been seen. The plaintext password is never transmitted upstream — only a short hash prefix is sent (k-anonymity).
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)password string nullable — Plaintext password to check (never sent upstream — only a short hash prefix leaves) (examples: "password"; minLength: 1)hash string nullable — Pre-computed password hash to check, as an alternative to password (examples: "5BAA61E4C9B93F3F0682250B6CF8331B7EE68FD8")mode string — Hashing scheme used to look up the password (default: "sha1"; one of: "sha1", "ntlm")@type string (default: "HaveibeenpwnedPassword")hash string requiredmode string required (one of: "sha1", "ntlm")is_pwned boolean (default: false)pwn_count integer (default: 0)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.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.