Format Guard API

API ID 14947

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

100% uptime 186 ms avg response

API Documentation

Endpoints

Request
Normalizes spacing, checks known-country length, and applies the ISO 13616 mod-97 checksum.
Endpoint ID: 39157
POST https://zylalabs.com/api/14947/format+guard+api/39157/validate+an+iban
INPUT PARAMETERS

Validate an IBAN — Endpoint Features

Object Description
Request Body Required Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

API EXAMPLE RESPONSE
JSON
{
    "ok": true,
    "data": {
        "valid": true,
        "compact": "GB82WEST12345698765432",
        "country": "GB",
        "checkDigits": "82",
        "length": 22,
        "expectedLength": 22,
        "checksumOk": true,
        "lengthOk": true,
        "issues": []
    }
}
Validate an IBAN — CODE SNIPPETS

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"}'

    
Request
Luhn checksum plus brand detection. Format only; the full number is never returned, only last4, brand, and the checksum result.
Endpoint ID: 39158
POST https://zylalabs.com/api/14947/format+guard+api/39158/validate+a+payment-card+number
INPUT PARAMETERS

Validate a payment-card number — Endpoint Features

Object Description
Request Body Required Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

API EXAMPLE RESPONSE
JSON
{
    "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."
    }
}
Validate a payment-card number — CODE SNIPPETS

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"}'

    
Request
Accepts hyphenated or compact ISBNs. ISBN-10 may end in X.
Endpoint ID: 39159
POST https://zylalabs.com/api/14947/format+guard+api/39159/validate+an+isbn-10+or+isbn-13
INPUT PARAMETERS

Validate an ISBN-10 or ISBN-13 — Endpoint Features

Object Description
Request Body Required Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

API EXAMPLE RESPONSE
JSON
{
    "ok": true,
    "data": {
        "valid": true,
        "type": "isbn-13",
        "compact": "9780306406157",
        "checksumOk": true,
        "issues": []
    }
}
Validate an ISBN-10 or ISBN-13 — CODE SNIPPETS

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"}'

    
Request
Checks 8-4-4-4-12 hex layout and reports version and variant. Optionally require a version (1-8).
Endpoint ID: 39160
POST https://zylalabs.com/api/14947/format+guard+api/39160/validate+a+uuid
INPUT PARAMETERS

Validate a UUID — Endpoint Features

Object Description
Request Body Required Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

API EXAMPLE RESPONSE
JSON
{
    "ok": true,
    "data": {
        "valid": true,
        "uuid": "550e8400-e29b-41d4-a716-446655440000",
        "version": 4,
        "variant": "rfc4122",
        "formatOk": true,
        "issues": []
    }
}
Validate a UUID — CODE SNIPPETS

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"}'

    
Request
Practical format check only. Does not query DNS or verify that a mailbox exists.
Endpoint ID: 39161
POST https://zylalabs.com/api/14947/format+guard+api/39161/validate+email+format
INPUT PARAMETERS

Validate email format — Endpoint Features

Object Description
Request Body Required Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

API EXAMPLE RESPONSE
JSON
{
    "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."
    }
}
Validate email format — CODE SNIPPETS

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]"}'

    
Request
Accepts 8, 12, 13, or 14 digit codes (EAN-8, UPC-A, EAN-13, or GTIN-14) and checks the GS1 checksum.
Endpoint ID: 39162
POST https://zylalabs.com/api/14947/format+guard+api/39162/validate+an+ean+upc+or+gtin
INPUT PARAMETERS

Validate an EAN UPC or GTIN — Endpoint Features

Object Description
Request Body Required Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

API EXAMPLE RESPONSE
JSON
{
    "ok": true,
    "data": {
        "valid": true,
        "type": "ean-13",
        "compact": "4006381333931",
        "checksumOk": true,
        "expectedCheckDigit": 1,
        "issues": []
    }
}
Validate an EAN UPC or GTIN — CODE SNIPPETS

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"}'

    
Request
Nine-digit ABA checksum only. Does not confirm that the institution exists.
Endpoint ID: 39163
POST https://zylalabs.com/api/14947/format+guard+api/39163/validate+a+us+aba+routing+number
INPUT PARAMETERS

Validate a US ABA routing number — Endpoint Features

Object Description
Request Body Required Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

API EXAMPLE RESPONSE
JSON
{
    "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."
    }
}
Validate a US ABA routing number — CODE SNIPPETS

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"}'

    
Request
Calendar dates (YYYY-MM-DD) and date-times with optional seconds, fraction, and Z or ±HH:MM offset. Checks month length and leap years.
Endpoint ID: 39164
POST https://zylalabs.com/api/14947/format+guard+api/39164/validate+an+iso+8601+date+or+date-time
INPUT PARAMETERS

Validate an ISO 8601 date or date-time — Endpoint Features

Object Description
Request Body Required Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

API EXAMPLE RESPONSE
JSON
{
    "ok": true,
    "data": {
        "valid": true,
        "value": "2026-11-15T16:15:00Z",
        "kind": "date-time",
        "issues": []
    }
}
Validate an ISO 8601 date or date-time — CODE SNIPPETS

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"}'

    
Request
Each item needs type and value. Types: iban, credit-card, isbn, uuid, email, ean, routing-number, iso8601.
Endpoint ID: 39165
POST https://zylalabs.com/api/14947/format+guard+api/39165/validate+up+to+50+values+at+once
INPUT PARAMETERS

Validate up to 50 values at once — Endpoint Features

Object Description
Request Body Required Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

API EXAMPLE RESPONSE
JSON
{
    "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": []
                }
            }
        ]
    }
}
Validate up to 50 values at once — CODE SNIPPETS

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"}]}'

    

API Access Key & Authentication

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.

Headers
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.

Starts at
$10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Overview

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

Format Guard API FAQs

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.

General FAQs

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

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.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

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.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs