{
"ok": true,
"data": {
"valid": true,
"compact": "GB82WEST12345698765432",
"country": "GB",
"checkDigits": "82",
"length": 22,
"expectedLength": 22,
"checksumOk": true,
"lengthOk": true,
"issues": []
}
}
curl --location --request POST 'https://zylalabs.com/api/14947/format+guard+api/39157/validate+an+iban' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"iban":"GB82 WEST 1234 5698 7654 32"}'
{
"ok": true,
"data": {
"valid": true,
"brand": "visa",
"last4": "1111",
"length": 16,
"luhnOk": true,
"issues": [],
"note": "Format and checksum only. This does not authorize a charge, confirm the card exists, or verify the cardholder."
}
}
curl --location --request POST 'https://zylalabs.com/api/14947/format+guard+api/39158/validate+a+payment-card+number' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"number":"4111 1111 1111 1111"}'
{
"ok": true,
"data": {
"valid": true,
"type": "isbn-13",
"compact": "9780306406157",
"checksumOk": true,
"issues": []
}
}
curl --location --request POST 'https://zylalabs.com/api/14947/format+guard+api/39159/validate+an+isbn-10+or+isbn-13' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"isbn":"978-0-306-40615-7"}'
{
"ok": true,
"data": {
"valid": true,
"uuid": "550e8400-e29b-41d4-a716-446655440000",
"version": 4,
"variant": "rfc4122",
"formatOk": true,
"issues": []
}
}
curl --location --request POST 'https://zylalabs.com/api/14947/format+guard+api/39160/validate+a+uuid' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"uuid":"550e8400-e29b-41d4-a716-446655440000"}'
{
"ok": true,
"data": {
"valid": true,
"email": "[email protected]",
"local": "dev",
"domain": "example.com",
"formatOk": true,
"issues": [],
"note": "Format only. This does not check DNS, MX records, or whether a mailbox exists."
}
}
curl --location --request POST 'https://zylalabs.com/api/14947/format+guard+api/39161/validate+email+format' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"email":"[email protected]"}'
{
"ok": true,
"data": {
"valid": true,
"type": "ean-13",
"compact": "4006381333931",
"checksumOk": true,
"expectedCheckDigit": 1,
"issues": []
}
}
curl --location --request POST 'https://zylalabs.com/api/14947/format+guard+api/39162/validate+an+ean+upc+or+gtin' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"code":"4006381333931"}'
{
"ok": true,
"data": {
"valid": true,
"compact": "021000021",
"checksumOk": true,
"issues": [],
"note": "Checksum only. This does not confirm the institution exists or that an account can be debited."
}
}
curl --location --request POST 'https://zylalabs.com/api/14947/format+guard+api/39163/validate+a+us+aba+routing+number' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"number":"021000021"}'
{
"ok": true,
"data": {
"valid": true,
"value": "2026-11-15T16:15:00Z",
"kind": "date-time",
"issues": []
}
}
curl --location --request POST 'https://zylalabs.com/api/14947/format+guard+api/39164/validate+an+iso+8601+date+or+date-time' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"value":"2026-11-15T16:15:00Z"}'
{
"ok": true,
"data": {
"count": 3,
"passed": 3,
"failed": 0,
"results": [
{
"index": 0,
"type": "iban",
"result": {
"valid": true,
"compact": "DE89370400440532013000",
"country": "DE",
"checkDigits": "89",
"length": 22,
"expectedLength": 22,
"checksumOk": true,
"lengthOk": true,
"issues": []
}
},
{
"index": 1,
"type": "email",
"result": {
"valid": true,
"email": "[email protected]",
"local": "dev",
"domain": "example.com",
"formatOk": true,
"issues": [],
"note": "Format only. This does not check DNS, MX records, or whether a mailbox exists."
}
},
{
"index": 2,
"type": "isbn",
"result": {
"valid": true,
"type": "isbn-13",
"compact": "9780306406157",
"checksumOk": true,
"issues": []
}
}
]
}
}
curl --location --request POST 'https://zylalabs.com/api/14947/format+guard+api/39165/validate+up+to+50+values+at+once' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"items":[{"type":"iban","value":"DE89370400440532013000"},{"type":"email","value":"[email protected]"},{"type":"isbn","value":"9780306406157"}]}'
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 Format Guard 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.
Checksum and format validation for IBAN, payment cards, ISBN, UUID, email, EAN/UPC, US routing numbers, and ISO 8601 dates. All checks are computed locally. A passing checksum does not mean an
No. This API only checks format and checksums. It does not contact banks, card networks, or payment processors, and it cannot authorize a charge.
No. Card numbers are used only to compute the Luhn check and brand, then discarded. The response includes last4, brand, length, and whether the checksum passed.
No. Email checks are format only. The API does not query DNS or MX records and does not confirm that a mailbox can receive mail.
HTTP 200 means the check ran successfully. The result is in data.valid. A false value means the string failed the checksum or format rules; issues lists the reasons. HTTP 400 is reserved for malformed requests.
Up to 50 items per call. Each item needs a type and a value. Types are iban, credit-card, isbn, uuid, email, ean, routing-number, and iso8601. UUID items may also include version.
Calendar dates as YYYY-MM-DD, and date-times with optional seconds, a fractional second, and a Z or ±HH:MM offset. Month lengths and leap years are checked. Values such as 15/11/2026 are rejected.
The API returns HTTP 413 and does not process the body. Keep each field at or under the documented length limits.
No. It is a pure compute utility. It does not look up institutions, cards, or mailboxes, and it does not store the values you send.
Each endpoint returns a JSON object containing a boolean `ok` field indicating success, and a `data` field with specific validation results. For example, the IBAN endpoint returns fields like `valid`, `compact`, `country`, and `issues`.
Key fields include `valid` (boolean), `compact` (normalized value), `length` (actual length), `expectedLength` (expected length), `checksumOk` (checksum validity), and `issues` (any validation issues encountered).
Each endpoint accepts a specific value to validate, such as an IBAN, credit card number, ISBN, UUID, email, EAN, routing number, or ISO 8601 date. Some endpoints allow optional parameters, like specifying a UUID version.
The response data is structured with an `ok` field for overall success, followed by a `data` object containing detailed validation results. Each result includes relevant fields specific to the type of validation performed.
The API provides validation for various identifiers: IBANs, payment cards, ISBNs, UUIDs, emails, EAN/UPCs, US routing numbers, and ISO 8601 dates. Each endpoint focuses on format and checksum validation.
Users can check the `valid` field to determine if the input is valid. Additional fields like `issues` provide insights into any problems, while `compact` offers a standardized format for further processing.
Typical use cases include validating user input in forms, ensuring data integrity in financial transactions, and verifying product identifiers in inventory systems. This helps prevent errors and improve data quality.
Data accuracy is maintained through local checksum calculations and format validations based on established standards (e.g., ISO 13616 for IBANs, Luhn algorithm for credit cards). The API does not rely on external data sources, ensuring consistent results.
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