USA Routing Number API

This API provides detailed information about bank routing numbers, including their validity and processing capabilities.

The Routing Number API is designed to handle data related to bank routing numbers, specifically focusing on their validity and associated banking information. It processes various data fields including routing number, bank name, telegraphic name, location, and different payment processing statuses such as FedACH, Fedwire, and funds transfer eligibility. The API adheres to the MICR (Magnetic Ink Character Recognition) format for routing numbers, which is a standard used in the banking industry for check processing. The data structure includes fields for routing number validation, bank identification, and payment processing capabilities, ensuring that users can access accurate and up-to-date information. Technical requirements include adherence to banking standards and formats, with constraints regarding the processing of FedACH payments. The output format is structured in JSON, providing a clear schema that includes all relevant data points for each routing number queried, enabling integration with financial applications and services.

API Documentation

Endpoints


This endpoint allows users to retrieve detailed information about a specific bank routing number. By providing a valid routing number as a parameter, users can access a wealth of information including the bank's name, telegraphic name, location, and various payment processing capabilities such as FedACH and Fedwire eligibility. This is particularly useful for financial institutions, businesses, and individuals who need to verify the validity of a routing number before processing transactions. The endpoint ensures that the information returned is accurate and up-to-date, adhering to the MICR format standards used in the banking industry. Users can expect a structured JSON response that includes all relevant data points associated with the queried routing number.


                                                                            
POST https://zylalabs.com/api/5813/usa+routing+number+api/7593/get+routing+number+details
                                                                            
                                                                        

Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"routing_number":"031101347","bank_name":"Td Bank Usa, National Association","telegraphic_name":"TD BANK USA, NA","location":"Wilmington, DE","fedach_eligible":"No","fedwire_eligible":"Eligible","funds_transfer_eligible":"Eligible"}
                                                                                                                                                                                                                    
                                                                                                    

Get routing number details - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/5813/usa+routing+number+api/7593/get+routing+number+details' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"routing":"Required"}'


API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the USA Routing Number API REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

πŸš€ Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • βœ”οΈŽ Only Pay for Successful Requests
  • βœ”οΈŽ Free 7-Day Trial
  • βœ”οΈŽ Multi-Language Support
  • βœ”οΈŽ One API Key, All APIs.
  • βœ”οΈŽ Intuitive Dashboard
  • βœ”οΈŽ Comprehensive Error Handling
  • βœ”οΈŽ Developer-Friendly Docs
  • βœ”οΈŽ Postman Integration
  • βœ”οΈŽ Secure HTTPS Connections
  • βœ”οΈŽ Reliable Uptime

USA Routing Number API FAQs

The USA Routing Number API is designed to provide detailed information about bank routing numbers, including their validity and associated banking information.

You can retrieve various data fields such as routing number, bank name, telegraphic name, location, and payment processing statuses like FedACH, Fedwire, and funds transfer eligibility.

The API adheres to the MICR (Magnetic Ink Character Recognition) format, which is a standard used in the banking industry for check processing, ensuring accurate and up-to-date information.

The API outputs data in a structured JSON format, which includes all relevant data points for each queried routing number, facilitating integration with financial applications.

Yes, the API requires adherence to banking standards and formats, with specific constraints regarding the processing of FedACH payments.

The API returns detailed information including the routing number, bank name, telegraphic name, location, and payment processing capabilities such as FedACH, Fedwire, and funds transfer eligibility.

Key fields in the response include "routing_number," "bank_name," "telegraphic_name," "location," "fedach_eligible," "fedwire_eligible," and "funds_transfer_eligible," providing comprehensive banking details.

The response data is structured in JSON format, with each key-value pair clearly representing specific attributes of the queried routing number, making it easy to parse and integrate into applications.

The API provides information on routing number validity, bank identification, location, and eligibility for various payment processing methods, essential for transaction verification.

Users can customize requests by providing a specific routing number as a parameter in the POST request, allowing for targeted retrieval of banking information associated with that number.

The data is sourced from official banking records and industry standards, ensuring that the information provided is reliable and adheres to established banking protocols.

Typical use cases include verifying routing numbers for transactions, integrating banking information into financial applications, and ensuring compliance with payment processing standards.

Users can leverage the returned data to validate routing numbers before processing transactions, assess bank capabilities for payments, and enhance financial application functionalities with accurate banking information.

General FAQs

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, refer to the β€˜X-Zyla-API-Calls-Monthly-Remaining’ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

To see the maximum number of API requests your plan allows, check the β€˜X-Zyla-RateLimit-Limit’ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.

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 3,600, it means 3,600 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 give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.

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 free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.

Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.


Related APIs