The Swift Code Lookup API is a powerful tool for businesses that need to make international payments. This API provides developers with a simple and efficient way to find the Bank Identifier Code (BIC) or SWIFT code of any financial institution in the world. The BIC or SWIFT code is a unique identification code used to identify banks and financial institutions globally, and it is required for international wire transfers.
The API works by searching a comprehensive database of financial institutions, and returning the BIC or SWIFT code of the requested institution. The API also provides additional information about the institution, such as its name, address, and country of origin. This information can be used to verify the legitimacy of the institution, and to ensure that the payment is being sent to the correct recipient.
The Swift Code Lookup API is easy to integrate into existing applications, with a simple RESTful interface that supports both XML and JSON formats. The API also includes comprehensive documentation, code examples, and support for multiple programming languages, making it easy for developers to get started.
This API is useful for a wide range of businesses, including banks, financial institutions, e-commerce platforms, and any organization that needs to make international payments. By using the Swift Code Lookup API, businesses can ensure that payments are processed quickly and accurately, while reducing the risk of errors and fraud.
In addition to payment processing, the Swift Code Lookup API can also be used for compliance monitoring and fraud prevention. By verifying the BIC or SWIFT codes of financial institutions, businesses can ensure that they are not unwittingly sending payments to fraudulent organizations or individuals. This can help protect businesses from financial loss and reputational damage.
Overall, the Swift Code Lookup API is a valuable tool for any business that needs to make international payments. By providing accurate and up-to-date information about financial institutions, this API can help businesses save time and money, while improving the accuracy and security of their payment processing.
Pass any SWIFT code to validate and receive if its valid or not and relevant information about the bank.
International Payments: The primary use case for the Swift Code Lookup API is to validate the BIC or SWIFT code of a financial institution before processing an international payment. This ensures that the payment is sent to the correct recipient and avoids any delays or rejections due to incorrect information.
Customer Onboarding: Banks and other financial institutions can use the Swift Code Lookup API during the customer onboarding process. By validating the BIC or SWIFT code of a new customer's bank account, financial institutions can ensure that the account is legitimate and active before opening it.
Compliance Monitoring: Compliance departments can use the Swift Code Lookup API to monitor for suspicious activity. By verifying the BIC or SWIFT codes of financial institutions, compliance departments can identify potential cases of fraud or money laundering and take appropriate action.
Risk Management: Financial institutions and other businesses that make international payments can use the Swift Code Lookup API as a risk management tool. By verifying the BIC or SWIFT codes of financial institutions, businesses can reduce the risk of errors or fraudulent activity.
International Trade: Businesses that engage in international trade can use the Swift Code Lookup API to ensure that payments are sent to the correct financial institutions. This can help to avoid any delays or rejections of payments, and ensure that transactions are processed quickly and accurately.
Besides the number of API calls, there is no other limitation
Pass the SWIFT code to validate and receive additional data from the bank.
Code Lookup - Endpoint Features
Object | Description |
---|---|
code |
[Required] The SWIFT Code to lookup. |
{"status":200,"success":true,"message":"SWIFT code AXISINBB301 is valid","data":{"swift_code":"AXISINBB301","bank":null,"city":null,"branch":null,"address":null,"post_code":null,"country":null,"country_code":null,"breakdown":{"swift_code":"AXISINBB301","bank_code":null,"country_code":null,"location_code":null,"code_status":null,"branch_code":null}}}
curl --location --request GET 'https://zylalabs.com/api/1714/swift+code+lookup+api/1327/code+lookup?code=ADTVBRDF' --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 Code Lookup endpoint returns data related to the validity of a SWIFT code, including the bank's name, city, branch, address, postal code, country, and country code. It also provides a breakdown of the SWIFT code components.
Key fields in the response include "status," "success," "message," and "data." Within "data," important fields are "swift_code," "bank," "city," "branch," "address," "post_code," and "country."
The response data is structured in a JSON format. It includes a top-level object with status information and a nested "data" object containing detailed information about the SWIFT code and the associated bank.
The Code Lookup endpoint provides information on the validity of a SWIFT code, the associated bank's name, location details, and a breakdown of the SWIFT code components, aiding in international payment verification.
Data accuracy is maintained through regular updates from reliable financial institution databases and validation checks to ensure that the SWIFT codes and associated information are current and correct.
Typical use cases include validating SWIFT codes for international payments, onboarding customers by verifying bank details, and compliance monitoring to prevent fraud or money laundering.
Users can utilize the returned data to confirm the legitimacy of financial institutions before processing payments, ensuring that the correct recipient is targeted and reducing the risk of errors.
Standard data patterns include a clear indication of whether the SWIFT code is valid, along with associated bank details. Users can expect structured responses with consistent field names across queries.
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.
Service Level:
100%
Response Time:
565ms
Service Level:
100%
Response Time:
1,938ms
Service Level:
100%
Response Time:
503ms
Service Level:
100%
Response Time:
539ms
Service Level:
100%
Response Time:
351ms
Service Level:
100%
Response Time:
366ms
Service Level:
100%
Response Time:
377ms
Service Level:
100%
Response Time:
521ms
Service Level:
100%
Response Time:
3,246ms
Service Level:
100%
Response Time:
209ms
Service Level:
100%
Response Time:
363ms
Service Level:
98%
Response Time:
144ms
Service Level:
100%
Response Time:
221ms
Service Level:
100%
Response Time:
19,141ms
Service Level:
100%
Response Time:
655ms
Service Level:
100%
Response Time:
17,617ms
Service Level:
100%
Response Time:
1,468ms
Service Level:
80%
Response Time:
260ms
Service Level:
100%
Response Time:
3,245ms
Service Level:
100%
Response Time:
166ms