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 |
[Optional] 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' |
{
"status": 200,
"success": true,
"message": "Routing Bank 026002532 is valid",
"data": {
"routing_number": "026002532",
"date_of_revision": "031110",
"new_routing_number": null,
"bank": "THE BANK OF NOVA SCOTIA",
"address": "ONE LIBERTY PLAZA",
"city": "NEW YORK",
"state": "NY",
"zip": "10006",
"phone": "(212) 225-5361"
}
}
curl --location --request GET 'https://zylalabs.com/api/331/routing+number+bank+lookup+api/266/get+bank+information?routingnumber=Required' --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 121000248 is valid","data":{"routing_number":"121000248","date_of_revision":"091012","new_routing_number":"","bank":"WELLS FARGO BANK, NA","address":"255 2ND AVE SOUTH","city":"MINNEAPOLIS","state":"MN","zip":"55479","phone":"(800) 745-2426"}}
curl --location --request GET 'https://zylalabs.com/api/331/routing+number+bank+lookup+api/1353/get+bank+information?number=Required' --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 commitments. One click upgrade/downgrade or cancellation. No questions asked.
The Routing Number Bank Lookup 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 Routing Number Bank Lookup API specifically focuses on routing numbers for financial institutions in the United States. It does not support international routing numbers from other countries.
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.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, look at the ‘X-Zyla-API-Calls-Monthly-Remaining’ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.
To see the maximum number of API requests your plan allows, check the ‘X-Zyla-RateLimit-Limit’ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.
The ‘X-Zyla-RateLimit-Reset’ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it’s important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
100%
Response Time:
214ms
Service Level:
100%
Response Time:
450ms
Service Level:
100%
Response Time:
513ms
Service Level:
100%
Response Time:
222ms
Service Level:
100%
Response Time:
271ms
Service Level:
100%
Response Time:
642ms
Service Level:
100%
Response Time:
897ms
Service Level:
100%
Response Time:
1,436ms
Service Level:
100%
Response Time:
317ms
Service Level:
100%
Response Time:
398ms
Service Level:
100%
Response Time:
1,221ms
Service Level:
100%
Response Time:
1,779ms
Service Level:
100%
Response Time:
162ms
Service Level:
100%
Response Time:
184ms
Service Level:
80%
Response Time:
493ms
Service Level:
100%
Response Time:
990ms
Service Level:
100%
Response Time:
740ms