Routing Number Lookup API
Overview
To use Routing Number Lookup, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/routinglookupExample
How to call the Routing Number Lookup API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/routinglookup?routing=121000358" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/routinglookup?routing=121000358', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/routinglookup?routing=121000358', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/routinglookup?routing=121000358", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"routing_number": "121000358",
"office_code": "O",
"record_type_code": "1",
"new_routing_number": "000000000",
"bank": "BANK OF AMERICA, N.A.",
"address": "8001 VILLA PARK DRIVE",
"city": "HENRICO",
"state": "VA",
"zip": "23228",
"zip_extension": "0000",
"country": "US"
}
}Authentication
The Routing Number Lookup API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Routing Number Lookup API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Routing Number Lookup API:
Lookup Routing Number Information
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
routing | string | required | The routing number to lookup information about Length: 9 - 9 chars | - |
Response
The Routing Number Lookup API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<routing_number>121000358</routing_number>
<office_code>O</office_code>
<record_type_code>1</record_type_code>
<new_routing_number>000000000</new_routing_number>
<bank>BANK OF AMERICA, N.A.</bank>
<address>8001 VILLA PARK DRIVE</address>
<city>HENRICO</city>
<state>VA</state>
<zip>23228</zip>
<zip_extension>0000</zip_extension>
<country>US</country>
</data>
</response>
status: ok
error: null
data:
routing_number: '121000358'
office_code: O
record_type_code: '1'
new_routing_number: '000000000'
bank: BANK OF AMERICA, N.A.
address: 8001 VILLA PARK DRIVE
city: HENRICO
state: VA
zip: '23228'
zip_extension: '0000'
country: US
| key | value |
|---|---|
| routing_number | 121000358 |
| office_code | O |
| record_type_code | 1 |
| new_routing_number | 000000000 |
| bank | BANK OF AMERICA, N.A. |
| address | 8001 VILLA PARK DRIVE |
| city | HENRICO |
| state | VA |
| zip | 23228 |
| zip_extension | 0000 |
| country | US |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
routing_number | string | The ABA routing number for the bank | |
office_codePremium | string | Office code designating the main office or branch location | |
record_type_codePremium | string | Record type code indicating transaction type classification | |
new_routing_numberPremium | string | New routing number if the bank has been updated | |
bank | string | Name of the financial institution or bank | |
addressPremium | string | Street address of the bank's main office location | |
cityPremium | string | City where the bank is located | |
state | string | Two-letter state abbreviation of bank location | |
zipPremium | string | Five-digit postal code of bank location | |
zip_extensionPremium | string | Four-digit ZIP code extension for more precise location | |
country | string | Country code (ISO 3166-1 alpha-2 format) |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Routing Number Lookup through GraphQL to combine it with other API calls in a single request. Query only the routing number lookup data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
routinglookup(
input: {
routing: "121000358"
}
) {
routing_number
office_code
record_type_code
new_routing_number
bank
address
city
state
zip
zip_extension
country
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Routing Number Lookup API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Routing Number Lookup requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Routing Number Lookup API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Routing Number Lookup
Official Routing Number Lookup packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Routing Number Lookup works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Routing Number Lookup?
How many credits does Routing Number Lookup cost?
Each successful Routing Number Lookup API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful routing number lookup lookups.
Can I use Routing Number Lookup in production?
The free plan is for testing and development only. For production use of Routing Number Lookup, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Routing Number Lookup from a browser?
What happens if I exceed my Routing Number Lookup credit limit?
When you reach your monthly credit limit, Routing Number Lookup API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








