Docs/APIs/Password Strength

Password Strength

Check Password Strength

OperationalCredits 1 per callp50 913msData ValidationStar

Overview

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.

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.

GEThttps://api.apiverve.com/v1/passwordstrength
curl "https://api.apiverve.com/v1/passwordstrength?password=Password123" \
  -H "x-api-key: your_api_key_here"
const res = await fetch('https://api.apiverve.com/v1/passwordstrength?password=Password123', {
  headers: { 'x-api-key': 'your_api_key_here' },
});

if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);

const { data } = await res.json();
console.log(data);
import requests

res = requests.get(
    "https://api.apiverve.com/v1/passwordstrength?password=Password123",
    headers={"x-api-key": "your_api_key_here"},
    timeout=15,
)
res.raise_for_status()

print(res.json()["data"])
package main

import (
	"fmt"
	"io"
	"net/http"
)

func main() {
	req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/passwordstrength?password=Password123", nil)
	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.

401 is the only auth verdict

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 in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.

ParameterTypeDescription
passwordRequiredstringThe password to check the strength of

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.

Sample response
{
  "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
  }
}

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.

FieldTypeExampleDescription
strengthstring"weak"Strength label: too weak, weak, medium or strong
scorenumber1Numeric strength score (0-3, higher is stronger)
passwordInfoobject{...}
lengthnumber11Number of characters in the password
hasSpecialCharactersbooleanfalseWhether the password contains special characters
hasNumbersbooleantrueWhether the password contains numbers
hasLowercasebooleantrueWhether the password contains lowercase letters
hasUppercasebooleantrueWhether the password contains uppercase letters
hasSpacesbooleanfalseWhether the password contains spaces
hasSequentialCharsbooleantrueWhether the password contains a run of 3+ sequential characters (e.g. abc, 123)
hasRepeatedCharsbooleanfalseWhether the password repeats the same character 3+ times in a row (e.g. aaa)
recommendationsPremiumarray[Use at least 12 characters, ...]List of recommendations to improve password strength
entropyBitsPremiumnumber65.5Theoretical 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

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.

StatusMeaningWhat to do
400Input was rejectedRead error; it names the parameter.
401Key missing or invalidCheck the header name and the key value.
403Key valid, but not permittedA key restriction or IP allow-list; see key scoping.
429Rate limited, or out of creditsRead error to tell them apart; see rate limits.

Other ways to use Password Strength

Set up Password Strength on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKitReference →
Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheetsReference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContextReference →

More in Data Validation:

Was this page helpful?