{
"code": 200,
"status": "success",
"data": {
"healthy": true
}
}
curl --location --request GET 'https://zylalabs.com/api/13743/securepass+generator+and+strength+auditor+api/31488/health+check' --header 'Authorization: Bearer YOUR_API_KEY'
{
"code": 200,
"status": "success",
"data": {
"passwords": [
"[ddP[9*09r|bK[_8"
]
}
}
curl --location --request POST 'https://zylalabs.com/api/13743/securepass+generator+and+strength+auditor+api/31489/generate+passwords' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"length": 16,
"count": 1,
"uppercase": true,
"lowercase": true,
"numbers": true,
"symbols": true,
"excludeAmbiguous": false
}'
{
"code": 200,
"status": "success",
"data": {
"score": 0,
"label": "very weak",
"feedback": [
"Password is very short — use at least 8 characters",
"Use at least 12 characters for better security",
"Mix uppercase, lowercase, numbers, and symbols"
]
}
}
curl --location --request POST 'https://zylalabs.com/api/13743/securepass+generator+and+strength+auditor+api/31490/score+password+strength' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"password": "hunter2"
}'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the SecurePass Generator and Strength Auditor API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
The "Health check" endpoint returns a status message indicating the API's operational health. The "Generate passwords" endpoint returns an array of securely generated passwords based on specified parameters. The "Score password strength" endpoint returns a numeric score, a label indicating strength, and feedback on how to improve the password.
Key fields include "code" (HTTP status), "status" (success or failure), and "data" (containing specific information like passwords or scoring details). For password scoring, "score," "label," and "feedback" are essential fields.
Users can customize requests with parameters such as "length" (4-128), "count" (1-50), "uppercase," "lowercase," "numbers," "symbols," and "excludeAmbiguous." Each parameter has sensible defaults, allowing flexibility in password generation.
Response data is structured in JSON format, with a top-level object containing "code," "status," and "data." The "data" field varies by endpoint, containing either generated passwords or scoring details, making it easy to parse and utilize.
Common use cases include generating secure passwords for new user accounts, populating test data, enforcing password policies during signup, and providing real-time feedback on password strength in user interfaces.
Users can leverage the generated passwords for secure account creation or testing. The scoring feedback helps improve password policies by identifying weaknesses, guiding users to create stronger passwords based on actionable suggestions.
Data accuracy is maintained through heuristic scoring that evaluates various factors like length, character variety, and common password lists. This approach ensures that the scoring reflects real-world password security practices without relying on extensive breach databases.
Users can expect scores ranging from 0 (very weak) to 4 (very strong), with corresponding feedback. Common patterns include suggestions for increasing length, mixing character types, and avoiding common passwords, helping users understand how to enhance their password security.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund