You need to validate a US routing number fast, return the bank’s name and contact info, and ship it into your onboarding, payouts, or payments ops this week. By the end of this guide, you’ll call a real “routing bank checker” endpoint, parse the response fields you care about, and know how to also validate IBAN and SWIFT codes from the same Finance API on Zyla API Hub.
What you can build with this Finance API
The SWIFT - IBAN - Routing Bank Checker API returns bank metadata for three kinds of identifiers:
- US routing numbers: confirm validity and fetch bank name, city/state, address, phone, and revision date.
- IBAN codes: check validity and extract bank code, branch code, account number, and country info.
- SWIFT/BIC codes: validate and retrieve bank name, location, address, country/country code, and a structured breakdown.
Developers use it to harden onboarding forms, prevent payout misroutes, reconcile vendor data, and surface clear error messages when account details don’t pass validation.
Getting started on Zyla API Hub
Zyla API Hub centralizes more than 10,000 public APIs under a single account, one API key, and a subscription + quota model (not pay-per-call). This Finance API offers a 7-day trial or 50 requests to let you validate the integration before you commit. To proceed:
- Open the API page: Start 7-day trial on SWIFT - IBAN - Routing Bank Checker API.
- Click Subscribe or Start Free Trial if available, and copy your API key.
- Use Authorization: Bearer YOUR_API_KEY in requests to the Hub endpoints.
You’ll call endpoints hosted under zylalabs.com. No separate origin or access key is needed—your Hub key covers this API.
Endpoints overview (Finance)
Below are the three endpoints you can call from the same API. All are HTTP GET requests and return JSON.
1) Routing Bank Checker
Validate a US routing number and retrieve bank details.
- Method: GET
- URL: https://zylalabs.com/api/1887/swift-iban-routing-bank-checker-api/1580/routing-bank-checker
- Required query param: number
Example required parameter:
- number (number, required): 121000248
Copy-pasteable cURL (official sample):
curl -s -X GET "https://zylalabs.com/api/1887/swift-iban-routing-bank-checker-api/1580/routing-bank-checker?number=121000248" \
-H "Authorization: Bearer YOUR_API_KEY"Official JSON response:
{
"status": 200,
"success": true,
"message": "Routing Bank 031101334 is valid",
"data": {
"routing_number": "031101334",
"date_of_revision": "Jan 5, 2023",
"new_routing_number": "",
"bank": "Sofi Bank, National Association",
"address": "San Francisco, CA",
"city": "San Francisco",
"state": "CA",
"zip": "",
"phone": "855-936-2269"
}
}Field highlights you’ll likely use:
- status and success: quick test for request outcome.
- message: human-readable validity note (useful for UI toasts or logs).
- data.routing_number: the validated number (can also reflect canonical/updated value).
- data.bank, data.city, data.state, data.address, data.phone: bank identity and contact info for KYC, support, or audits.
- data.date_of_revision and data.new_routing_number: track updates or redirects if present.
2) IBAN Code Checker
Validate an IBAN and receive parsed components.
- Method: GET
- URL: https://zylalabs.com/api/1887/swift-iban-routing-bank-checker-api/1581/iban-code-checker
- Required query param: number
Example required parameter:
- number (string, required): PT50000101231234567890192
This endpoint returns whether the IBAN is valid and its breakdown (e.g., country, bank code, branch code, account number). Integrate it to pre-validate EU/SEPA details before payouts or partner onboarding.
3) SWIFT Code Checker
Validate a SWIFT/BIC code and retrieve bank profile and a detailed breakdown.
- Method: GET
- URL: https://zylalabs.com/api/1887/swift-iban-routing-bank-checker-api/1582/swift-code-checker
- Required query param: code
Example required parameter:
- code (string, required): ADTVBRDF
Use this to verify international transfer destinations and to auto-fill bank data in forms, reducing manual errors and support tickets.
Python example: validate a routing number and parse the fields
This snippet calls the Routing Bank Checker endpoint, checks success, and prints the bank’s details. Replace YOUR_API_KEY with your key from Zyla API Hub.
import requests
API_KEY = "YOUR_API_KEY"
URL = "https://zylalabs.com/api/1887/swift-iban-routing-bank-checker-api/1580/routing-bank-checker"
params = {"number": "121000248"}
headers = {"Authorization": f"Bearer {API_KEY}"}
resp = requests.get(URL, params=params, headers=headers, timeout=10)
resp.raise_for_status()
payload = resp.json()
if payload.get("success"):
data = payload.get("data", {})
print("Validated routing number:", data.get("routing_number"))
print("Bank:", data.get("bank"))
print("Location:", f'{data.get("city")}, {data.get("state")}')
print("Address:", data.get("address"))
print("Phone:", data.get("phone"))
print("Date of revision:", data.get("date_of_revision"))
new_rn = data.get("new_routing_number")
if new_rn:
print("New routing number:", new_rn)
else:
print("Validation failed:", payload.get("message"))Notes that save time:
- Authorization header is required: Authorization: Bearer YOUR_API_KEY.
- Responses include status, success, message, and data. Use these rather than guessing HTTP codes for every failure reason.
- Cache known-good validations short-term (e.g., minutes to hours) to reduce repeats in high-traffic flows.
- If you store results, keep date_of_revision and new_routing_number to track potential changes.
Practical integration patterns
Inline validation in onboarding forms
- On blur of the routing number field, hit the Routing Bank Checker endpoint.
- Show bank, city, state as read-only confirmation to the user.
- Surface the message field for clear feedback if invalid.
Pre-flight checks before payouts
- Validate routing/IBAN/SWIFT ahead of scheduling transfers.
- Log the message and data.routing_number (or IBAN/SWIFT) you validated to assist reconciliation.
Back-office reconciliation
- Use bank identity fields (bank, city, state/country) to enrich vendor records.
- Alert ops if new_routing_number appears so they can contact the vendor for updates.
Error handling and reliability tips
- Transport errors: handle timeouts and non-2xx responses with retries and backoff.
- Application-level errors: check success and message; display message in admin tools for clarity.
- Idempotency: reads are safe to retry; avoid hammering on every keystroke—debounce form inputs.
- Pagination: not applicable here—single checks per identifier.
- Timestamps/units: date_of_revision is a human-readable date string (e.g., “Jan 5, 2023”). Parse if you need consistent formats.
Security and compliance basics
- Do not log full account numbers in plaintext; only store routing/IBAN/SWIFT as needed.
- Restrict API key usage to server-side or secure agent environments. Rotate keys regularly.
- If you build user-facing flows, rate-limit at your edge and cache positive validations judiciously.
Calling the Finance API from an AI agent (MCP)
If you’re using Claude Code, Cursor, Windsurf, or any MCP-compatible client, you can route calls through the MCP endpoint. Point your agent to:
https://mcp.zylalabs.com/mcp?apikey=YOUR_API_KEY
From there, instruct the agent to invoke the SWIFT - IBAN - Routing Bank Checker API tools with the same endpoint paths shown above. This keeps your key centralized and lets multiple AI-first dev tools call the same Finance API via MCP. For an overview, see: MCP.
Endpoint details you’ll use most
Routing Bank Checker
- GET https://zylalabs.com/api/1887/swift-iban-routing-bank-checker-api/1580/routing-bank-checker
- Params: number (required)
- Use cases: US ACH/wire validation, bank autofill, support lookups.
- Response fields: routing_number, bank, city, state, address, phone, date_of_revision, new_routing_number.
IBAN Code Checker
- GET https://zylalabs.com/api/1887/swift-iban-routing-bank-checker-api/1581/iban-code-checker
- Params: number (required)
- Use cases: SEPA/EEA payouts, EU vendor onboarding.
- Response fields: iban, country, sepa_country, checksum, bban, bank_code, branch_code, account_number.
SWIFT Code Checker
- GET https://zylalabs.com/api/1887/swift-iban-routing-bank-checker-api/1582/swift-code-checker
- Params: code (required)
- Use cases: cross-border remittances, beneficiary bank verification.
- Response fields: swift_code, bank, city, branch, address, post_code, country, country_code, breakdown (with bank_code, location_code, etc.).
Testing strategies
- Start with the provided sample parameter values to confirm your auth and parsing flow.
- Exercise negative cases: try malformed numbers/codes and verify that you handle message and success correctly.
- Monitor which validations repeat in production and add short-term caching to cut response times and quotas.
Operational considerations on Zyla API Hub
- Billing: subscription + quota model, not pay-per-call.
- First API access: 7-day trial or 50 requests; check the API page for current access options and pricing.
- Centralized auth: one key for every API on the Hub; rotate via your account settings.
FAQ
Q1: What header do I need for authentication?
A: Send Authorization: Bearer YOUR_API_KEY in every request to the Hub endpoints.
Q2: Can I validate IBAN and SWIFT from the same integration?
A: Yes. This Finance API exposes three GET endpoints: routing bank checker, IBAN code checker, and SWIFT code checker. Each uses a single required query parameter.
Q3: How do I handle changes to routing numbers?
A: Check data.new_routing_number. If present, prompt users to update records and log the change along with data.date_of_revision.
Q4: Is there a free plan?
A: There is no Free Plan. This API uses a subscription + quota model. The first API access offers a 7-day trial or 50 requests—see the listing for details.
Q5: Can I call it from an AI coding agent?
A: Yes. Use the MCP endpoint at https://mcp.zylalabs.com/mcp?apikey=YOUR_API_KEY with your agent. See the overview here: MCP.
Ship it
Validate routing numbers, IBANs, and SWIFT codes with one API key and clear, structured responses. Copy the cURL above, drop in your key, and plug the fields into your forms and payout checks. When you’re ready, start here: Start 7-day trial on SWIFT - IBAN - Routing Bank Checker API.
