Validate a US ABA routing number
API · /financialid-api
Financial ID Validator API
healthy
3,913 Subscribers
Validate the bank and provider identifiers that move money and records — all checked locally, with no lookups. The bic endpoint validates and parses a SWIFT/BIC code (ISO 9362): it confirms the 8- or 11-character format, splits out the bank, country, location and branch codes, checks the country against ISO 3166, and flags test and passive-participant codes. The aba endpoint validates a US ABA routing number by its checksum (the 3-7-1 weighting) and names the Federal Reserve district from the prefix. The npi endpoint validates a US National Provider Identifier by its Luhn check digit over the 80840 prefix and reports whether it is an individual or organization NPI. Everything is computed locally and deterministically, so it is instant and private — it checks the structure and check digits, not whether the institution actually exists. Ideal for payments and banking, fintech onboarding and KYC forms, healthcare billing and clearinghouses, and form and data validation. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This validates BIC, ABA and NPI; for IBAN use an IBAN API and for payment-card numbers use a credit-card API.
api.oanor.com/financialid-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 92 ms
- Server probes · 24h
- Subscribers
- 3,913
- active
- Total calls
- 44
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 7,335 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 7,335 calls/month
- 2 req/sec
- BIC + ABA + NPI
- No credit card
Starter
€8.85 /month
- 16,850 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 16.85k calls/month
- 8 req/sec
- Structural + check-digit validation
- Email support
Pro
€28.75 /month
- 219,500 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 219.5k calls/month
- 20 req/sec
- Payments / KYC pipelines
- Priority support
Mega
€66.75 /month
- 1,140,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 1.14M calls/month
- 50 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
SWIFT/BIC Validator API
SWIFT/BIC business-identifier-code validation and parsing as an API, computed locally and deterministically. The validate endpoint checks that a code follows the ISO 9362 BIC structure — four letters for the institution, a two-letter ISO country code, a two-character location code and an optional three-character branch code, eight or eleven characters in total — ignoring spaces and upper-casing the input, and confirms the country code is a recognised one; DEUTDEFF (Deutsche Bank, Frankfurt) is a valid eight-character head-office BIC and DEUTDEFF500 a valid eleven-character branch BIC. The parse endpoint breaks a BIC into its institution, country, location and branch components, reports whether it is a head office or a branch (branch XXX or none means the head office), and reads the status from the location code’s second character — 0 for a test/non-SWIFT code, 1 for a passive participant and 2 for reverse billing. A BIC carries no checksum, so this is structural validation. Everything is computed locally and deterministically, so it is instant and private. Ideal for fintech, banking, payment, KYC, treasury and accounting app developers, SWIFT-code and bank-identifier tools, and onboarding flows. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 endpoints. This validates and parses a BIC; for IBAN account-number validation use an IBAN API.
api.oanor.com/bic-api
IBAN Validation API
Validate IBANs with the ISO 7064 mod-97 checksum and per-country length and structure checks, and resolve the BIC and bank details for supported countries. A local parse endpoint works for every IBAN country offline; the validate endpoint adds bank-code verification and BIC. Ideal for payments, billing, onboarding and KYC.
api.oanor.com/iban-api
ABA Routing Number API
US bank ABA routing-number (routing transit number) validation as an API, computed locally and deterministically. The validate endpoint checks a nine-digit routing number with the official ABA checksum — 3·(d1+d4+d7) + 7·(d2+d5+d8) + (d3+d6+d9) must be a multiple of ten — ignoring hyphens and spaces, and reads the first two digits as the Federal Reserve routing symbol to name the district (01–12 are the twelve Federal Reserve Banks from Boston to San Francisco, 21–32 are thrift institutions); JPMorgan Chase’s 021000021 validates and resolves to the Federal Reserve Bank of New York, and a number with a wrong check digit is rejected. The checkdigit endpoint computes the ninth check digit from the first eight so the whole number passes. It also returns the institution identifier (digits 5–8) and the check digit. Everything is computed locally and deterministically, so it is instant and private. Ideal for fintech, banking, ACH, payroll, payment and accounting app developers, bank-account-form validation and onboarding tools, and US payment software. This is the checksum and routing-symbol structure only — it does not confirm a live bank. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 endpoints. For SWIFT/BIC codes use a BIC API and for IBANs an IBAN API.
api.oanor.com/routingnumber-api
FDIC BankFind API
US banking data as an API, powered by the FDIC BankFind Suite — the official open data service of the Federal Deposit Insurance Corporation. Search the roughly 4,500 FDIC-insured banks by name and state (active, inactive or all), getting each bank's FDIC certificate number, name, city and state, total assets and deposits, branch-office count, charter class and founding year, ranked by size; read a single bank's full profile including its address, website, established and (if applicable) closed dates, total assets, deposits, equity and net income, branch count, charter class and type, primary federal regulator, deposit-insurance fund and business specialization; track a bank's quarterly financial performance over time — assets, deposits, equity, net income, net loans, return on assets, return on equity and net interest margin; and browse the complete history of US bank failures since 1934, with each failure's date, resolution type, acquiring institution, total assets and deposits and the FDIC's estimated cost — including recent high-profile failures such as Silicon Valley Bank, Signature Bank and First Republic Bank. Ideal for fintech, financial research, risk analysis, journalism and compliance tooling. Identify a bank by its FDIC certificate number from search results; all dollar figures are reported in thousands of US dollars. Data is public-domain from the FDIC (US institutions only).
api.oanor.com/fdic-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Financial ID Validator API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Financial ID Validator API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Financial ID Validator API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Financial ID Validator API cost?
Financial ID Validator API has a free tier with 100 calls / month. Paid plans start at €8.85 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Financial ID Validator API GDPR-compliant?
All requests to Financial ID Validator API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/financialid-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/financialid-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/financialid-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);import requests
r = requests.get(
"https://api.oanor.com/financialid-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
📌 Pinned
🔒 Locked
·
·
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.