{
"valid": true,
"luhn_valid": true,
"network": {
"id": "visa",
"name": "Visa"
},
"length": 16,
"length_valid_for_network": true,
"formatted": "4111 1111 1111 1111",
"masked": "411111******1111",
"iin": "411111",
"checked": {
"luhn_required": true
},
"privacy": "Le numéro n’est ni stocké ni journalisé."
}
curl --location --request POST 'https://zylalabs.com/api/15134/clearcheck+card+number+validator+luhn+api/40377/validate+a+card+number' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"number":"4111 1111 1111 1111"}'
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 ClearCheck Card Number Validator Luhn 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.
It returns JSON containing the overall `valid` result, `luhn_valid`, detected `network`, digit `length`, network-specific length status, normalized `formatted` and `masked` values, the first six digits as `iin`, and validation metadata such as `checked.luhn_required`.
The API can identify Visa, Mastercard, American Express, Discover, JCB, Diners Club, UnionPay, Maestro, Mir, RuPay, and Verve. The response provides a network `id` and display `name` when the number matches a supported network pattern.
`valid` represents the combined validation result. It considers the Luhn checksum and whether the number length is valid for the detected network. A number may pass Luhn but still be invalid if its length does not match the network’s expected length.
The network detection endpoint identifies a likely card network from the number’s leading digits. It is useful when you need network classification without performing the complete Luhn and length validation workflow.
`formatted` contains a normalized, human-readable representation, such as `4111 1111 1111 1111`. `masked` hides the middle digits, such as `411111******1111`. The `iin` field contains the first six digits used for identification.
No. The API checks the number’s structure, Luhn checksum, expected network length, and network pattern. It does not verify that the card was issued, is active, has funds, or can authorize transactions.
Errors are returned as JSON in the structure `{"error":{"code","message"}}`. Applications should inspect the error code and message, rather than assuming that a missing or incomplete validation result means the card number is invalid.
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