quick financial openapi Financial Validation API Postman Collection

API ID 13400

Comprehensive Financial Validation API for validating IFSC codes, IBANs, and US routing numbers. The IFSC validation includes format checks and optional reference lookups, while IBAN validation ensures structural integrity and checksum accuracy without confirming account existence. The routing number endpoints incorporate checksum validation alongside a FedACH-based bank directory for accurate routing information.

31 ms avg response

API Documentation

Endpoints

Request
The "Check IFSC Code" endpoint allows users to validate and retrieve detailed information about a specific Indian Financial System Code (IFSC), which is used for electronic fund transfers between banks in India. This endpoint processes an input IFSC code and returns pertinent details such as the bank's name, branch location, and associated address, ensuring that the provided code is both valid and accurately reflects the current banking structure. Common use cases for this endpoint include confirming the legitimacy of a bank branch during fund transfers, integrating banking functionalities within financial applications, and enhancing user experience on platforms that facilitate online payments or banking services.
Endpoint ID: 28735
GET https://docs.zylalabs.com/api/13400/quick+financial+openapi+financial+validation+api+postman+collection/28735/check+ifsc+code
INPUT PARAMETERS

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

This endpoint does not require any input parameters.

API EXAMPLE RESPONSE
JSON
{
    "input": "HDFC0001234",
    "normalized": "HDFC0001234",
    "valid": true,
    "reason": "ok",
    "reference_match": true,
    "reference_status": "matched",
    "branch": {
        "ifsc_code": "HDFC0001234",
        "bank_name": "HDFC Bank",
        "branch_name": "PARK STREET",
        "city": "JAIPUR",
        "district": "JAIPUR",
        "state": "RAJASTHAN",
        "source": "razorpay_ifsc"
    },
    "attribution": [
        {
            "source": "Reserve Bank of India (RBI)",
            "dataset": "Bank branch and IFSC reference publications",
            "license": "Public reference data (verify latest RBI terms)",
            "url": "https://www.rbi.org.in/",
            "notice": "IFSC checks include format validation and can be augmented with RBI reference datasets for branch-level verification."
        },
        {
            "source": "Federal Reserve Financial Services",
            "dataset": "FedACH Routing Directory",
            "license": "U.S. federal reference data",
            "url": "https://www.frbservices.org/resources/routing-number-directory",
            "notice": "US routing-number checks use checksum validation and can be matched against FedACH routing directory records for bank-level lookup."
        },
        {
            "source": "ISO 13616 / IBAN specification",
            "dataset": "IBAN structure and checksum rules",
            "license": "Specification-derived validation logic",
            "notice": "IBAN endpoint validates structure and checksum only and does not confirm account existence."
        }
    ]
}
Check IFSC Code — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/13400/quick+financial+openapi+financial+validation+api+postman+collection/28735/check+ifsc+code' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
The "Verify IBAN Format" endpoint is designed to validate the structure of an International Bank Account Number (IBAN) based on established international standards. This endpoint checks the format for correctness, ensuring that the IBAN adheres to the specified length and includes the appropriate country and bank codes. Upon processing a request, it returns a response indicating whether the IBAN format is valid or invalid, along with any relevant error messages for invalid inputs. This functionality is particularly useful for financial institutions, payment processors, and e-commerce platforms that need to ensure correct bank details are captured to reduce transaction errors and enhance security during monetary transfers.
Endpoint ID: 28736
GET https://docs.zylalabs.com/api/13400/quick+financial+openapi+financial+validation+api+postman+collection/28736/verify+iban+format
INPUT PARAMETERS

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

This endpoint does not require any input parameters.

API EXAMPLE RESPONSE
JSON
{
    "input": "GB82WEST12345698765432",
    "normalized": "GB82WEST12345698765432",
    "country_code": "GB",
    "expected_length": 22,
    "actual_length": 22,
    "checksum_valid": true,
    "valid": true,
    "reason": "ok",
    "attribution": [
        {
            "source": "Reserve Bank of India (RBI)",
            "dataset": "Bank branch and IFSC reference publications",
            "license": "Public reference data (verify latest RBI terms)",
            "url": "https://www.rbi.org.in/",
            "notice": "IFSC checks include format validation and can be augmented with RBI reference datasets for branch-level verification."
        },
        {
            "source": "Federal Reserve Financial Services",
            "dataset": "FedACH Routing Directory",
            "license": "U.S. federal reference data",
            "url": "https://www.frbservices.org/resources/routing-number-directory",
            "notice": "US routing-number checks use checksum validation and can be matched against FedACH routing directory records for bank-level lookup."
        },
        {
            "source": "ISO 13616 / IBAN specification",
            "dataset": "IBAN structure and checksum rules",
            "license": "Specification-derived validation logic",
            "notice": "IBAN endpoint validates structure and checksum only and does not confirm account existence."
        }
    ]
}
Verify IBAN Format — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/13400/quick+financial+openapi+financial+validation+api+postman+collection/28736/verify+iban+format' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
The "Verify Routing Number" endpoint is designed to validate the authenticity and eligibility of a provided bank routing number, ensuring it conforms to the standards set by the American Bankers Association (ABA). When a valid routing number is submitted, this endpoint processes the input and returns pertinent information such as the financial institution's name, address, and the type of transactions supported (e.g., ACH, wire transfers). This endpoint is particularly useful for businesses and financial applications that require accurate bank details for processing payments, setting up direct deposits, or facilitating electronic fund transfers, thereby reducing errors and enhancing operational efficiency.
Endpoint ID: 28737
GET https://docs.zylalabs.com/api/13400/quick+financial+openapi+financial+validation+api+postman+collection/28737/verify+routing+number
INPUT PARAMETERS

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

This endpoint does not require any input parameters.

API EXAMPLE RESPONSE
JSON
{
    "input": "021000021",
    "normalized": "021000021",
    "checksum_valid": true,
    "valid": true,
    "reason": "ok",
    "reference_status": "matched",
    "reference_match": true,
    "bank": {
        "routing_number": "021000021",
        "customer_name": "JPMORGAN CHASE",
        "city": "TAMPA",
        "state": "FL",
        "zip_code": "336100000",
        "phone": "8134323700",
        "institution_status_code": "1",
        "source": "fedach",
        "updated_at": "2026-07-29T17:19:03.916039Z"
    },
    "attribution": [
        {
            "source": "Reserve Bank of India (RBI)",
            "dataset": "Bank branch and IFSC reference publications",
            "license": "Public reference data (verify latest RBI terms)",
            "url": "https://www.rbi.org.in/",
            "notice": "IFSC checks include format validation and can be augmented with RBI reference datasets for branch-level verification."
        },
        {
            "source": "Federal Reserve Financial Services",
            "dataset": "FedACH Routing Directory",
            "license": "U.S. federal reference data",
            "url": "https://www.frbservices.org/resources/routing-number-directory",
            "notice": "US routing-number checks use checksum validation and can be matched against FedACH routing directory records for bank-level lookup."
        },
        {
            "source": "ISO 13616 / IBAN specification",
            "dataset": "IBAN structure and checksum rules",
            "license": "Specification-derived validation logic",
            "notice": "IBAN endpoint validates structure and checksum only and does not confirm account existence."
        }
    ]
}
Verify routing number — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/13400/quick+financial+openapi+financial+validation+api+postman+collection/28737/verify+routing+number' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Returns bank profile fields for a US routing number from the ingested FedACH directory.
Endpoint ID: 28738
GET https://docs.zylalabs.com/api/13400/quick+financial+openapi+financial+validation+api+postman+collection/28738/retrieve+bank+details+by+routing+number
INPUT PARAMETERS

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

This endpoint does not require any input parameters.

API EXAMPLE RESPONSE
JSON
{
    "input": "021000021",
    "found": true,
    "bank": {
        "routing_number": "021000021",
        "customer_name": "JPMORGAN CHASE",
        "address": "3RD FLOOR",
        "city": "TAMPA",
        "state": "FL",
        "zip_code": "336100000",
        "phone": "8134323700",
        "office_code": "O",
        "record_type_code": "1",
        "servicing_frb_number": "021001208",
        "institution_status_code": "1",
        "data_view_code": "1",
        "source": "fedach",
        "updated_at": "2026-07-29T17:19:03.916039Z"
    },
    "attribution": [
        {
            "source": "Reserve Bank of India (RBI)",
            "dataset": "Bank branch and IFSC reference publications",
            "license": "Public reference data (verify latest RBI terms)",
            "url": "https://www.rbi.org.in/",
            "notice": "IFSC checks include format validation and can be augmented with RBI reference datasets for branch-level verification."
        },
        {
            "source": "Federal Reserve Financial Services",
            "dataset": "FedACH Routing Directory",
            "license": "U.S. federal reference data",
            "url": "https://www.frbservices.org/resources/routing-number-directory",
            "notice": "US routing-number checks use checksum validation and can be matched against FedACH routing directory records for bank-level lookup."
        },
        {
            "source": "ISO 13616 / IBAN specification",
            "dataset": "IBAN structure and checksum rules",
            "license": "Specification-derived validation logic",
            "notice": "IBAN endpoint validates structure and checksum only and does not confirm account existence."
        }
    ]
}
Retrieve bank details by routing number — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/13400/quick+financial+openapi+financial+validation+api+postman+collection/28738/retrieve+bank+details+by+routing+number' --header 'Authorization: Bearer YOUR_API_KEY' 


    

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 quick financial openapi Financial Validation API Postman Collection 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.

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

(Save 2 months with annual billing 🎉)

🚀 Enterprise Plan

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring
zeiss-logo amazon-logo zoom-logo decathlon-logo

Trusted by leading companies

Overview

Comprehensive Financial Validation API for validating IFSC codes, IBANs, and US routing numbers. The IFSC validation includes format checks and optional reference lookups, while IBAN validation ensures structural integrity and checksum accuracy without confirming account existence. The routing number endpoints incorporate checksum validation alongside a FedACH-based bank directory for accurate routing information.

quick financial openapi Financial Validation API Postman Collection FAQs

Each endpoint returns specific financial validation data. The IFSC endpoint provides details like bank name, branch location, and validity status. The IBAN endpoint returns format validity, expected length, and checksum status. The routing number endpoints offer bank name, address, and transaction types supported.

Key fields include "valid" and "reason" for validation status, "bank_name" and "branch_name" for IFSC, "country_code" and "checksum_valid" for IBAN, and "customer_name" and "address" for routing numbers. These fields help users assess the accuracy of financial information.

The returned data is structured in JSON format, containing nested objects for detailed information. Each response includes fields like "input," "valid," and specific details related to the financial code being validated, ensuring clarity and ease of use.

The IFSC endpoint provides bank and branch details, the IBAN endpoint checks format and checksum validity, while the routing number endpoints deliver bank information and transaction capabilities. This comprehensive data supports various financial operations.

Data is sourced from reputable institutions such as the Reserve Bank of India (RBI) for IFSC codes and the Federal Reserve for routing numbers. These sources ensure high accuracy and reliability in the validation process.

Data accuracy is maintained through regular updates from authoritative sources and validation checks, such as format and checksum verifications. This ensures that users receive reliable and up-to-date financial information.

Typical use cases include validating bank details for fund transfers, integrating banking functionalities in applications, and ensuring correct payment processing in e-commerce. This helps reduce errors and enhances user experience.

Users can utilize the returned data by checking the "valid" field to confirm the accuracy of financial codes. They can also leverage detailed information like bank names and addresses for transaction processing and customer verification.

General FAQs

To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key 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.

The free trial lasts for 7 days and allows you to make up to 50 API requests.

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. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.

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.

You can monitor your API usage through the response headers included with every request:

x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.

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 subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.

Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.

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.
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]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs