
Call FreeDailyPro validation endpoints for IBAN, VIN, GTIN, routing, email, phone, GSTIN and PAN from one API key.
Maya Chen builds checkout and onboarding forms for a logistics SaaS team in Austin, Texas. Bad IBANs, mistyped VINs, and barcode strings with a wrong check digit used to reach the warehouse queue before anyone noticed. The FreeDailyPro Validation endpoints on the developers surface let her POST an identifier, get a clear valid flag and structured fields back, and stop the bad row early—with the same API key her service already uses for text and document work.
Live coverage on the developers page groups bank, barcode, vehicle, email, phone, and tax identifiers. The OpenAPI list includes:
POST /v1/validate/iban — country length from the IBAN registry plus mod 97-10 check digits; returns country, BBAN, and 4-character grouping.POST /v1/validate/bic — BIC/SWIFT shape and ISO country; splits institution, country, location, branch. Format only; does not prove the bank exists.POST /v1/validate/routing-number — US ABA 3-7-1 checksum; institution type from prefix and Federal Reserve district. No bank-name lookup.POST /v1/validate/gtin — GS1 check digit for UPC-A, EAN-13, EAN-8, GTIN-14; notes ISBN/ISSN prefixes. No product catalog lookup.POST /v1/validate/vin — length, forbidden I/O/Q, position-9 check digit (required for North America); region, model year, manufacturer and plant codes. No make/model database.POST /v1/validate/email — syntax (including international domains), disposable/role/webmail flags, optional MX-style domain check; never contacts the mailbox.POST /v1/validate/phone — libphonenumber plans; E.164, national, international formats and line type. Does not call the number.POST /v1/validate/gstin — Indian GSTIN format, state code, embedded PAN, check character. Does not query the GST portal.POST /v1/validate/pan — Indian PAN format and holder type. Does not check with the tax department.Every description on the live API states the same privacy line: the request is processed and nothing is stored as a permanent record of the identifier you sent.
GB82 WEST 1234 5698 7654 32, BIC DEUTDEFF, US routing 021000021 for a separate US vendorvalid: false before finance exports a payout fileX-API-Key (not Bearer)A wrong check digit returns valid: false with a reason she can log. A correct shape with a real bank that later fails KYC is still possible—the endpoint never promised existence of the account.
https://api.freedailypro.com./v1/validate/iban with JSON {"iban":"GB82 WEST 1234 5698 7654 32"} and header X-API-Key: YOUR_API_KEY.valid, reason, country, check digits, BBAN, and the grouped form. Every answer wraps its fields in a top-level result object./v1/validate/vin or /v1/validate/gtin when the form field changes; keep one client wrapper that only swaps the path and payload field name (vin for VIN, code for GTIN, routingNumber for routing numbers, bic for BIC). Unknown fields are rejected with a 400.Example curl shape for IBAN:
curl -X POST https://api.freedailypro.com/v1/validate/iban \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"iban":"GB82 WEST 1234 5698 7654 32"}'
The endpoints say the same thing in their own notes: the BIC answer reads “Format check only. It does not confirm that this bank exists,” and the routing-number answer reads “It does not confirm that the number is assigned to a bank.” Maya copies that honesty into her form messages. Email MX checks can confirm a domain accepts mail in general; they still cannot prove a specific mailbox exists. Phone validation formats numbers; it does not ring them.
valid: true on BIC or PAN as “this company is approved.”Authorization: Bearer instead of X-API-Key.On blur, Maya’s web form calls a thin backend that hits the validation path and returns only { ok, message }. The browser never holds the platform API key. For bulk CSV imports, a worker walks rows and writes a column iban_valid before finance sees the file. Failures include the API reason text so support can tell a vendor “check digit failed” instead of “invalid.”
She validates only rows that changed since the last import hash. Unchanged IBANs skip the call. On a trial key, 20,000 monthly calls is plenty for onboarding volume if you do not re-check every row every night. Paid tiers exist when nightly full re-checks become a product requirement.
Does IBAN validation prove the account can receive funds? No. It checks length and mod 97-10 check digits (and related fields). Banks and payment processors still run their own verification.
How many validation endpoints are there?
Nine live paths under /v1/validate/ for IBAN, BIC, routing number, GTIN, VIN, email, phone, GSTIN, and PAN.
Is the call stored? The live descriptions state the request is processed and nothing is stored as a retained copy of the identifier.
Bad identifiers are cheap to reject early and expensive to unwind after payout. Open developers, create a key, and run one IBAN and one VIN call against sample values before you wire production forms.
If you want a sample Node wrapper for all nine paths next, ask at https://www.freedailypro.com/contact.