Overview
The password is hashed with SHA-1 on our side and only the first 5 characters of the hash are sent to the Pwned Passwords range API, with response padding on, so the password itself never leaves the request. It is not logged, stored or returned. You can also send the SHA-1 yourself so the plain password never reaches us.
Live Test Password Breach Checker API →
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl -X POST https://api.apiverve.com/v1/passwordbreach \
-H "x-api-key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"password": "password123"
}'const res = await fetch('https://api.apiverve.com/v1/passwordbreach', {
method: 'POST',
headers: {
'x-api-key': 'your_api_key_here',
'Content-Type': 'application/json',
},
body: JSON.stringify({
"password": "password123"
}),
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.post(
"https://api.apiverve.com/v1/passwordbreach",
headers={"x-api-key": "your_api_key_here"},
json={
"password": "password123"
},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
"strings"
)
func main() {
body := strings.NewReader(`{
"password": "password123"
}`)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/passwordbreach", body)
req.Header.Set("Content-Type", "application/json")
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Parameters
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
passwordOptional | string | The password to check. Hashed on receipt and never stored. Send this or hash length 0–1024 |
hashOptional | string | The 40-character hex SHA-1 of the password, instead of the password itself |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"breached": true,
"breachCount": 2266543,
"riskLevel": "critical",
"inputType": "password",
"hashPrefix": "CBFDA"
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
breached | boolean | true | True when the password appears in the breach corpus |
breachCountPremium | number | 2266543 | Number of times the password appears in the breach corpus |
riskLevelPremium | string | "critical" | Exposure bracket: none, low (1-9), medium (10-999), high (1,000-99,999) or critical (100,000+) |
inputType | string | "password" | Whether a password or a hash was checked |
hashPrefix | string | "CBFDA" | The 5-character SHA-1 prefix that was sent to the range API |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- Sign-Up and Password Change
- Reject or warn on passwords that have appeared in breaches when a user creates an account or changes their password, as NIST SP 800-63B recommends.
- Login Risk Scoring
- Flag accounts whose current password is known to be breached and prompt a reset before credential stuffing finds them.
- Password Audits
- Check stored SHA-1 hashes from a legacy system against the breach corpus without handling plain passwords.
- Password Managers
- Mark saved passwords that have leaked so users know which ones to change first.
Other ways to use Password Breach Checker
Set up Password Breach Checker on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Security: