Routing Number LookupRouting Number Lookup API

OnlineCredit Usage:5 per callRefreshed Just now
avg: 1821ms|p50: 1657ms|p75: 1930ms|p90: 2258ms|p99: 2914ms

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

URL
https://api.apiverve.com/v1/routinglookup

Example

How to call the Routing Number Lookup API in different programming languages.

cURL Request
curl -X GET \
  "https://api.apiverve.com/v1/routinglookup?routing=121000358" \
  -H "X-API-Key: your_api_key_here"
JavaScript (Fetch API)
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);
Python (Requests)
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)
Go (net/http)
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))
}
Example 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"
  }
}

Authentication

The Routing Number Lookup API requires authentication via API key. Include your API key in the request header:

Required Header
X-API-Key: your_api_key_here

Learn more about authentication →

Interactive 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

ParameterTypeRequiredDescriptionDefaultExample
routingstringrequired
The routing number to lookup information about
Length: 9 - 9 chars
-121000358

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 Response
200 OK
<?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>
YAML Response
200 OK
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
CSV Response
200 OK
keyvalue
routing_number121000358
office_codeO
record_type_code1
new_routing_number000000000
bankBANK OF AMERICA, N.A.
address8001 VILLA PARK DRIVE
cityHENRICO
stateVA
zip23228
zip_extension0000
countryUS

Response Structure

All API responses follow a consistent structure with the following fields:

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains 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:

Response fields marked with Premium are available exclusively on paid plans.View pricing
FieldTypeSample ValueDescription
routing_numberstring"121000358"
The ABA routing number for the bank
office_codePremiumstring"O"
Office code designating the main office or branch location
record_type_codePremiumstring"1"
Record type code indicating transaction type classification
new_routing_numberPremiumstring"000000000"
New routing number if the bank has been updated
bankstring"BANK OF AMERICA, N.A."
Name of the financial institution or bank
addressPremiumstring"8001 VILLA PARK DRIVE"
Street address of the bank's main office location
cityPremiumstring"HENRICO"
City where the bank is located
statestring"VA"
Two-letter state abbreviation of bank location
zipPremiumstring"23228"
Five-digit postal code of bank location
zip_extensionPremiumstring"0000"
Four-digit ZIP code extension for more precise location
countrystring"US"
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.

Test Routing Number Lookup in the GraphQL Explorer to confirm availability and experiment with queries.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

GraphQL Endpoint
POST https://api.apiverve.com/v1/graphql
GraphQL Query Example
query {
  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?
Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for Routing Number Lookup and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
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?
Yes! The Routing Number Lookup API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.
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.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?