Identifiers validate aba routing
Exactidentifiers_validate_aba_routingDeterministic and authoritative — the canonical answer for this input.
Validate a US ABA/ACH bank routing number: 9 digits plus the weighted-sum mod-10 checksum (weights 3,7,1). Returns the Federal Reserve district derived from the first two digits. Processing multiple inputs? Use `identifiers_validate_aba_routing_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/aba-routing \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{"value":"021000021"}'The Batch tab sends up to 1000 inputs in one call via /v1/identifiers/validate/aba-routing/batch.
Example response
{
"input": "021000021",
"is_valid": true,
"normalized": "021000021",
"fed_district_code": "02",
"fed_district": "New York",
"aba_number": "02100002",
"check_digit": "1"
}FAQ
What does this check?
Whether a nine-digit US bank routing number passes its built-in checksum, and it also names the Federal Reserve district from the first two digits.
Does a valid result mean the bank account is real?
No. It confirms the routing number is mathematically well-formed, not that it belongs to an active bank or matches a specific account. This is a structural check, not a bank lookup.
How reliable is the answer?
It is exact and deterministic. The checksum either passes or it does not, so a valid number always reads valid.
What if I paste something that is not nine digits?
It returns is_valid false with a plain reason and confidence 0, rather than throwing an error.