Password Strength API Documentation
Everything you need to integrate password strength analysis and quantum resistance estimates into your application.
đ Overview
MyPasswordChecker.com provides a powerful REST API for password security analysis. Our API enables you to:
đ Password Analysis
Real-time strength scoring, entropy calculation, and crack time estimation using industry-standard algorithms.
âī¸ Quantum Estimates
Theoretical quantum computing resistance analysis using Grover's algorithm across multiple scenarios.
⨠Password Generation
Transform memorable phrases into quantum-resistant passwords with phonetic substitution techniques.
đ Authentication
All API requests require authentication using your API key. You can obtain an API key from the Developer Dashboard.
API Key Format
API keys follow the format: mpc_{32_hex_characters}
Including Your API Key
Add your API key to request headers using one of these methods:
Or using Bearer token format:
⥠Quick Start
Make your first API request in seconds:
1. Get Your API Key
Sign up at the Developer Dashboard to receive your free API key with 25 requests per month.
2. Make Your First Request
3. Parse the Response
đ Rate Limits
Rate limits vary by plan tier. All responses include rate limit headers:
| Header | Description |
|---|---|
X-RateLimit-Limit |
Total requests allowed this month |
X-RateLimit-Remaining |
Requests remaining this month |
X-RateLimit-Reset |
Unix timestamp when quota resets |
See our Pricing page for detailed quota information per plan.
đ Password Check API
POST /api/v1/check-password
Analyze password strength using advanced pattern detection and entropy calculation.
Request Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
password |
string | Yes | The password to analyze |
Response Fields
| Field | Type | Description |
|---|---|---|
strength |
string | Strength category: "very weak", "weak", "medium", "strong", "very strong" |
score |
integer | Numeric score from 0 (worst) to 4 (best) |
entropy |
float | Entropy in bits (higher is better) |
crack_time |
object | Estimated time to crack with modern hardware |
feedback |
object | Warnings and suggestions for improvement |
âī¸ Quantum Estimate API
POST /api/v1/estimate-quantum
Calculate theoretical quantum computing resistance using Grover's algorithm.
Request Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
password |
string | Yes | The password to analyze |
Response Structure
⨠Phonetic Generator API
POST /api/v1/generate-phonetic
Transform memorable phrases into strong, quantum-resistant passwords.
Request Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
phrase |
string | Yes | Memorable phrase to convert |
aggressiveness |
string | No | "low", "medium" (default), or "high" |
count |
integer | No | Number of variations (1-5, default: 5) |
Example Response
đ Breach Check API
POST /api/v1/breach-check
Check if a password appears in known data breaches using the Have I Been Pwned database with k-anonymity privacy protection.
Request Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
password_hash |
string | Yes | SHA-1 hash of password (40 hex characters) |
Example Request
Example Response (Password Found in Breaches)
Example Response (Password Not Found)
Response Fields
| Field | Type | Description |
|---|---|---|
pwned |
boolean | Whether password appears in breaches |
breach_count |
integer | Number of times password found in breaches |
message |
string | User-friendly message about breach status |
privacy_details |
object | Information about k-anonymity protection used |
usage |
object | Your current breach check quota usage |
Quota Limits by Tier
| Tier | Monthly Breach Checks |
|---|---|
| Free API | 50 |
| Standard | 2,500 |
| Basic Quantum | 10,000 |
| Standard Quantum | 25,000 |
| Large Quantum | 50,000 |
| Super Quantum | 200,000 |
đĄ Best Practices
Security Recommendations
- Never send passwords from client-side: Always call our API from your backend to protect API keys
- Use HTTPS: Our API only accepts HTTPS connections for secure data transmission
- Implement rate limit handling: Check response headers and handle 429 errors gracefully
- Rotate API keys: Periodically regenerate keys if you suspect compromise
Integration Tips
- Cache responses: Password strength doesn't change; cache results for identical passwords
- Set timeouts: Configure reasonable request timeouts (recommended: 5 seconds)
- Monitor usage: Track your API usage in the Dashboard
- Verify domains: Add your domains in Domain Verification for fraud protection
đģ Code Examples
JavaScript (Node.js)
Python
cURL
â ī¸ Error Handling
The API uses standard HTTP status codes:
| Status Code | Description | Action |
|---|---|---|
200 |
Success | Request processed successfully |
400 |
Bad Request | Check request parameters |
401 |
Unauthorized | Verify your API key is correct |
403 |
Forbidden | Domain not verified or tier access denied |
429 |
Rate Limit Exceeded | Wait until quota resets or upgrade plan |
500 |
Server Error | Retry with exponential backoff |
Error Response Format
đ Support
Need help? Here are your options:
đ Documentation
Review our API Reference for detailed endpoint specifications
đ Dashboard
Monitor usage and manage your account in the Developer Dashboard
đ° Pricing
View plans and features on our Pricing page
đ Security
Read our Privacy Policy and Terms of Service