Password Generator
Generate strong passwords and passphrases, then check how strong any password is before you use it.
- Next.js
- TypeScript
Also uses Password Generator
Catch weak passwords at signup before accounts are created.
Password Strength is a password strength checker API that scores how strong a password is. It returns a strength label and score, a breakdown of the character types used, weak-pattern detection, theoretical entropy in bits, and recommendations to improve it. Paid plans also check the password against over 2 billion breached passwords and return how often it has been seen.
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
"strength": "weak",
"score": 1,
"passwordInfo": {
"length": 11,
"hasSpecialCharacters": false,
"hasNumbers": true,
"hasLowercase": true,
"hasUppercase": true,
"hasSpaces": false,
"hasSequentialChars": true,
"hasRepeatedChars": false
},
"recommendations": [
"Use at least 12 characters",
"Add special characters",
"Avoid sequential characters (e.g. abc, 123)"
],
"entropyBits": 65.5
}
}
Generate strong passwords and passphrases, then check how strong any password is before you use it.
Also uses Password Generator
Password Strength works by analyzing the password provided — its length, character-set composition, and weak patterns like sequential or repeated characters. It returns a strength label, score, theoretical charset entropy and actionable recommendations. The password is never stored or returned.
Password Generator & Breach Checker for Windows rates and replaces weak passwords.
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
Same data, same APIVerve account, same credit balance — one key works on all of them.
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
| Parameter | Type | Example | Description |
|---|---|---|---|
passwordRequired | string | Password123 | The password to check the strength of |
curl "https://api.apiverve.com/v1/passwordstrength?password=Password123" \
-H "x-api-key: YOUR_API_KEY"Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
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.
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"strength": "weak",
"score": 1,
"passwordInfo": {
"length": 11,
"hasSpecialCharacters": false,
"hasNumbers": true,
"hasLowercase": true,
"hasUppercase": true,
"hasSpaces": false,
"hasSequentialChars": true,
"hasRepeatedChars": false
},
"recommendations": [
"Use at least 12 characters",
"Add special characters",
"Avoid sequential characters (e.g. abc, 123)"
],
"entropyBits": 65.5
}
}
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 |
|---|---|---|---|
strength | string | "weak" | Strength label: too weak, weak, medium or strong |
score | number | 1 | Numeric strength score (0-3, higher is stronger) |
passwordInfo | object | {...} | Character composition of the password: length and which character classes and patterns it contains |
length | number | 11 | Number of characters in the password |
hasSpecialCharacters | boolean | false | Whether the password contains special characters |
hasNumbers | boolean | true | Whether the password contains numbers |
hasLowercase | boolean | true | Whether the password contains lowercase letters |
hasUppercase | boolean | true | Whether the password contains uppercase letters |
hasSpaces | boolean | false | Whether the password contains spaces |
hasSequentialChars | boolean | true | Whether the password contains a run of 3+ sequential characters (e.g. abc, 123) |
hasRepeatedChars | boolean | false | Whether the password repeats the same character 3+ times in a row (e.g. aaa) |
recommendationsPremium | array | [Use at least 12 characters, ...] | List of recommendations to improve password strength |
entropyBitsPremium | number | 65.5 | Theoretical charset entropy in bits (length times log2 of the character-set size). This is the ceiling assuming random character selection; it does not account for dictionary words or common patterns, so use the strength/score for real-world guidance |
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Password Strength calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
No SDK to install — this is a plain HTTPS call to /v1/passwordstrength with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/passwordstrength" \
-H "x-api-key: YOUR_API_KEY"Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Install the Node.js SDK, then call the Password Strength API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/passwordstrengthconst res = await fetch("https://api.apiverve.com/v1/passwordstrength", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Install the Python SDK, then call the Password Strength API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-passwordstrengthimport requests
res = requests.get(
"https://api.apiverve.com/v1/passwordstrength",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Install the C# / .NET SDK, then call the Password Strength API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.PasswordStrengthusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/passwordstrength");
Console.WriteLine(json);Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/passwordstrength with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/passwordstrength", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/passwordstrength with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/passwordstrength");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/passwordstrength with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/passwordstrength")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyOnly the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Drop an interactive Password Strength form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Password Strength API.
Add Secure Password Generation to Your AppGenerate cryptographically secure passwords via API. Tutorial with code examples for signup flows, admin panels, and password managers.Read
Preventing Fake Signups: Registration Fraud GuideLearn how to stop bots and fraudsters while maintaining conversion rates for legitimate users.Read
Email Validation Best Practices: Beyond Simple RegexEmail validation beyond regex. Learn how to verify deliverability without rejecting legitimate users.Read