SWIFT Code Lookup API

About the SWIFT Code Lookup API

A SWIFT bank API and BIC lookup that gets bank data from a SWIFT code in one call. Pass an 8 or 11-character SWIFT/BIC code to retrieve the institution's name, branch, city and two-letter country code; an 8-character code also lists the branches under it. Or supply an institution name to search for its SWIFT codes across branches. The directory holds about 113,000 BIC records from the public ISO 9362 list, covering 232 countries and territories, and each search returns up to 25 matches with a count.

What people use it for

Cross-Border Wire Verification

Before initiating an international wire, billing platforms verify the recipient's SWIFT code matches the intended legal entity and destination country.

Vendor Onboarding Form

Auto-fill the bank name, branch city, and country code as soon as a supplier enters their SWIFT code during payment registration.

Branch Code Discovery

Accounting software helps treasury operators locate missing branch SWIFT codes by querying institutional names across international divisions.

Bank Country Screening

Risk engines cross-check the SWIFT country code against sanction lists to flag transfers directed to prohibited financial jurisdictions.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON

Default REST response

XML

Markup format

YAML

Human-readable

CSV

Tabular export

Beta

GraphQL

Query language

New

MCP

For AI agents

How it compares

Side by side with the tools people weigh SWIFT Code Lookup against — what each one is better at, in plain terms.

Request parameters — GET /v1/swiftlookup

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

1
2

curl "https://api.apiverve.com/v1/swiftlookup?swift=CHASUS33ARP" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Response — GET /v1/swiftlookup

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

{
  "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"
      }
    ]
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

What a call costs — 10 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Zero-code embed — one snippet, no backend

Drop an interactive SWIFT Code Lookup form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.

Changelog — SWIFT Code Lookup API

Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.

Currently v1