In the United States, a routing number (also called routing transit number) is a nine-digit code that identifies financial institutions. It is mainly used to facilitate the transfer of money between financial institutions through systems such as ACH, Fedwire, checks, etc. The routing number can be found at the bottom of a check.
This API will help you detect the information that is provided in the Routing number.
Just insert the routing number and the payment method, it could be ACH or Wire Transfer and it will deliver all the bank data associated to that Routing number.
With this API you will have the opportunity to validate the Routing number of your provider before making any transactions.
You will be able to determine where the account is located. You will have access to the bank information.
You will get additional information about the bank to make any quick call to check anything you need.
Besides the number of API calls per month, there are no other limitations.
This endpoint provides detailed information about a bank by using the bank's routing number. It can also be used to validate whether the bank supports ACH or Wire transfers. You can specify the type of payment (ACH or Wire), and the response format (JSON or XML).
This is useful for confirming bank details and validating routing numbers for different types of transactions.
The API response will return the status "fail" only if you enter a routing number that does not exist. However, if you enter an existing routing number that does not support the specified payment type, the API response will show the status "success" along with a clarification indicating that the entered routing number does not support that payment type (ach or wire).
Get Bank Information - Endpoint Features
| Object | Description |
|---|---|
routingnumber |
[Required] |
paymentType |
[Required] hoose to retrieve either the ACH or Wire Transfer information from the bank. Default value is ACH. Possible values: 'ach' and 'wire' |
format |
Optional Defines the format of the response. Default value is json. Possible inputs are 'xml' and 'json' |
source |
Optional Enter a source (1, 2, 3, 4 or 5). |
{"status":"success","data":{"routingNumber":"121000248","paymentType":"wire","name":"Wells Fargo Bank, Na","addressFull":"255 2nd Ave SouthMinneapolis, MN 55479","phone":"800-745-2426","type":"Main Office","servicingFedsMainOffice":"121000374","active":true,"lastUpdated":"2012-09-10"}}
curl --location --request GET 'https://zylalabs.com/api/7211/bank+routing+verification+api/11356/get+bank+information?routingnumber=121000248&paymentType=wire&format=json&source=1' --header 'Authorization: Bearer YOUR_API_KEY'
This endpoint allows you to retrieve detailed information about any bank by looking up its routing number. It also validates whether the provided routing number is correct, offering essential details such as the bank's name, address, and contact information. This is a useful tool for verifying routing numbers and ensuring they correspond to the correct financial institution.
Get Bank Information - Endpoint Features
| Object | Description |
|---|---|
number |
[Required] The routing number that you want to lookup |
{"status":200,"success":true,"message":"Routing Bank 044000024 is valid","data":{"routing_number":"044000024","date_of_revision":"032910","new_routing_number":"","bank":"HUNTINGTON NATIONAL BANK","address":"7 EASTON OVAL","city":"COLUMBUS","state":"OH","zip":"43219","phone":"(614) 331-8590"}}
curl --location --request GET 'https://zylalabs.com/api/7211/bank+routing+verification+api/11362/get+bank+information?number=043404647' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Bank Routing Verification API is a service that allows you to retrieve bank information based on a routing number input. It provides details about financial institutions in the United States.
The API helps you identify and retrieve information associated with a routing number. It is commonly used to validate provider routing numbers, recognize the bank associated with a routing number, and obtain additional bank information.
The API delivers comprehensive bank data associated with the provided routing number. This includes details such as the bank's name, location, and additional information that can be useful for verification or reference purposes.
The API supports both XML and JSON responses. You can choose the format that best suits your application's needs or preferences.
No, the Bank Routing Verification API specifically focuses on routing numbers for financial institutions in the United States. It does not support international routing numbers from other countries.
Each endpoint returns detailed bank information associated with a routing number, including the bank's name, address, city, state, zip code, and phone number. It also indicates whether the routing number supports ACH or Wire transfers.
Key fields in the response data include "routing_number," "bank," "address," "city," "state," "zip," "phone," and "success." These fields provide essential information for verifying bank details.
The endpoint accepts two parameters: "routing_number" (the nine-digit routing number) and "payment_type" (either ACH or Wire). These parameters allow users to customize their requests based on the transaction type.
The response data is structured in a JSON or XML format, with a top-level object containing "status," "success," "message," and "data." The "data" object includes detailed bank information, making it easy to parse.
Each endpoint provides information about the bank associated with a routing number, including its name, address, contact details, and whether it supports ACH or Wire transfers, ensuring comprehensive bank verification.
Data accuracy is maintained through regular updates and validation against official banking records. The API ensures that the routing numbers and associated bank information are current and reliable.
Typical use cases include validating a provider's routing number before transactions, identifying the bank associated with a routing number, and obtaining contact information for customer service inquiries.
Users can utilize the returned data to confirm bank details before initiating transactions, ensuring compliance with payment processing requirements, and facilitating communication with the bank for any inquiries.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
163ms
Service Level:
100%
Response Time:
3,133ms
Service Level:
100%
Response Time:
80ms
Service Level:
100%
Response Time:
619ms
Service Level:
100%
Response Time:
75ms
Service Level:
100%
Response Time:
160ms
Service Level:
100%
Response Time:
347ms
Service Level:
100%
Response Time:
458ms
Service Level:
100%
Response Time:
1,100ms
Service Level:
100%
Response Time:
595ms
Service Level:
100%
Response Time:
500ms
Service Level:
100%
Response Time:
459ms
Service Level:
100%
Response Time:
965ms
Service Level:
100%
Response Time:
3,420ms
Service Level:
100%
Response Time:
488ms
Service Level:
100%
Response Time:
513ms
Service Level:
100%
Response Time:
585ms
Service Level:
100%
Response Time:
601ms
Service Level:
100%
Response Time:
381ms
Service Level:
100%
Response Time:
1,045ms