SWIFT Code Lookup API
Overview
To use SWIFT Code Lookup, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/swiftlookupExample
How to call the SWIFT Code Lookup API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/swiftlookup?swift=CHASUS33ARP" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/swiftlookup?swift=CHASUS33ARP', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/swiftlookup?swift=CHASUS33ARP', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/swiftlookup?swift=CHASUS33ARP", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"count": 1,
"banks": [
{
"bank": "JPMORGAN CHASE BANK, N.A.",
"city": "NEW YORK,NY",
"branch": "ACCOUNT RECONCILIATION PROCESSING",
"swift_code": "CHASUS33ARP",
"country": "United States",
"country_code": "US"
}
]
}
}Authentication
The SWIFT Code Lookup API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the SWIFT Code Lookup API directly in your browser with live requests and responses.
Parameters
The SWIFT Code Lookup API supports multiple query options. Use one of the following:
Option 1: Lookup SWIFT Code Information
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
swift | string | required | The SWIFT code to lookup information about | - |
Option 2: Lookup SWIFT Code Information by Bank Name
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
bank | string | required | The name of the bank to lookup the SWIFT code information | - |
Response
The SWIFT Code Lookup API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<count>1</count>
<banks>
<bank>
<bank>JPMORGAN CHASE BANK, N.A.</bank>
<city>NEW YORK,NY</city>
<branch>ACCOUNT RECONCILIATION PROCESSING</branch>
<swift_code>CHASUS33ARP</swift_code>
<country>United States</country>
<country_code>US</country_code>
</bank>
</banks>
</data>
</response>
status: ok
error: null
data:
count: 1
banks:
- bank: JPMORGAN CHASE BANK, N.A.
city: NEW YORK,NY
branch: ACCOUNT RECONCILIATION PROCESSING
swift_code: CHASUS33ARP
country: United States
country_code: US
| key | value |
|---|---|
| count | 1 |
| banks | [{bank:JPMORGAN CHASE BANK, N.A.,city:NEW YORK,NY,branch:ACCOUNT RECONCILIATION PROCESSING,swift_code:CHASUS33ARP,country:United States,country_code:US}] |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
count | number | Total number of matching SWIFT code records returned | |
| [ ] Array items: | array[1] | Array of banks matching the SWIFT code lookup | |
â”” bank | string | Full legal name of the bank institution | |
â”” city | string | City and state location of the bank branch | |
â”” branch | string | Specific branch name and department information | |
â”” swift_code | string | The SWIFT/BIC code for the bank branch | |
â”” country | string | Country name where the bank is located | |
â”” country_code | string | ISO 3166-1 alpha-2 country code |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access SWIFT Code Lookup through GraphQL to combine it with other API calls in a single request. Query only the swift code lookup data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
swiftlookup(
input: {
swift: "CHASUS33ARP"
}
) {
count
banks
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The SWIFT Code Lookup API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
SWIFT Code Lookup requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The SWIFT Code Lookup API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for SWIFT Code Lookup
Official SWIFT Code Lookup packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
SWIFT Code Lookup works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for SWIFT Code Lookup?
How many credits does SWIFT Code Lookup cost?
Each successful SWIFT Code Lookup API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful swift code lookup lookups.
Can I use SWIFT Code Lookup in production?
The free plan is for testing and development only. For production use of SWIFT Code Lookup, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use SWIFT Code Lookup from a browser?
What happens if I exceed my SWIFT Code Lookup credit limit?
When you reach your monthly credit limit, SWIFT Code Lookup API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








