Identifiers validate iban
Exactidentifiers_validate_ibanDeterministic and authoritative — the canonical answer for this input.
Validate an International Bank Account Number (ISO 13616). Checks country-specific length, allowed characters, and the mod-97 checksum. Accepts spaces (banks print in 4-char groups). Returns country code, check digits, BBAN, and a pretty-grouped form. Processing multiple inputs? Use `identifiers_validate_iban_batch` to do up to 1000 in one call.
Parameters
valuestringrequiredThe identifier string to validate.
Call it
curl -X POST https://api.snipget.ai/v1/identifiers/validate/iban \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{"value":"DE89 3704 0044 0532 0130 00"}'The Batch tab sends up to 1000 inputs in one call via /v1/identifiers/validate/iban/batch.
Example response
{
"input": "DE89 3704 0044 0532 0130 00",
"is_valid": true,
"normalized": "DE89370400440532013000",
"pretty": "DE89 3704 0044 0532 0130 00",
"country": "DE",
"check_digits": "89",
"bban": "370400440532013000",
"length": 22
}FAQ
What does it confirm?
That an international bank account number has the right length for its country and passes the official mod-97 checksum. It also returns the country, the check digits, and a tidy spaced version for display.
Does a pass mean the account exists?
No. It confirms the IBAN is correctly formed, not that the account is open or owned by anyone in particular. It is a format and checksum check, not a bank lookup.
Can I paste it with spaces?
Yes. Banks print IBANs in four-character groups, so spaces are stripped automatically before checking.
How trustworthy is the verdict?
It is exact and deterministic. The checksum is authoritative, so a single mistyped character is reliably caught.
What about an unknown country code?
If the first two letters are not a country with a published IBAN format, you get is_valid false with a clear reason and confidence 0.