IFSC Lookup API

GET

Verify bank branch and contact details from any Indian IFSC code.

IFSC Lookup verifies Indian bank branch details from any IFSC code, returning the bank name, branch, street address, and district. It confirms city and state records, while paid plans add transfer modes like NEFT and UPI.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/ifsclookup?ifsc=SBIN0005943

Query parameters

ifscstring

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "status": "ok",
  "error": null,
  "data": {
    "bank": "State Bank of India",
    "ifsc": "SBIN0005943",
    "branch": "KASTURBA GANDHI MARG,NEW DELHI",
    "address": "23, HIMALAYA HOUSE KASTURBA GANDHI MARG NEW DELHI ,PIN - 110001",
    "contact": "",
    "city": "NEW DELHI",
    "district": "NEW DELHI",
    "state": "DELHI",
    "imps": true,
    "rtgs": true,
    "neft": true,
    "upi": true,
    "micr": "110002062",
    "swift": ""
  }
}

About the IFSC Lookup API

Pass any valid 11-character IFSC code to fetch registered branch information. The lookup checks weekly updated banking records to return the institution name, branch address, contact details, city, district, and state. Paid plans also return MICR, SWIFT codes, and payment rail flags including IMPS, RTGS, NEFT, and UPI.

What people use it for

Vendor Payout Verification: When onboarding Indian vendors, accounts payable teams confirm the bank name and branch location against supplied payout details before issuing wire transfers.
Checkout Routing: Fintech checkout forms auto-populate branch, city, and state values as soon as a customer enters their IFSC code.
Payroll Account Auditing: Audit employee direct deposit submissions by validating branch addresses and districts to reduce payout rejections from incorrect bank routing codes.
Merchant Settlement Setup: Payment gateways check branch credentials during merchant onboarding to verify account legitimacy before enabling settlement processing.

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
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use IFSC Lookup

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the IFSC Lookup API.

Read the docs →

What would 10,000 IFSC lookups a month cost me?

A volume of 10,000 lookups uses 100,000 credits, which fits well within the Starter plan allowance of 200,000 credits. That works out to about $0.0015 per call or $1.50 per 1,000 lookups. The Free plan includes 20 lookups per month for testing.

Are transfer modes like UPI, NEFT, and SWIFT included on the Free plan?

No, supported transfer flags for IMPS, RTGS, NEFT, and UPI, along with MICR and SWIFT codes, are premium fields. The Free plan returns core branch details such as bank name, branch location, and contact information. Any paid plan unlocks the full routing and payment attributes.

What bank information does a single IFSC lookup return?

Each query returns the bank name, branch name, contact details, city, district, and state. On paid plans, responses also include MICR and SWIFT codes alongside flags showing whether the branch supports IMPS, RTGS, NEFT, and UPI transactions.

How often is the branch routing data updated?

The database updates weekly to capture changes across Indian financial institutions. This regular refresh keeps branch locations and supported payment mechanisms aligned with active banking operations.

Can I use this branch data in my production payout or onboarding flow?

Yes, commercial use is permitted across all paid plans. You can use the returned bank and branch data inside your checkout forms, payout verification pipelines, or internal tools, provided you do not resell the raw data as a standalone directory.

Request parameters — GET /v1/ifsclookup

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

Parameter	Type	Example	Description
`ifsc`Required	string	`SBIN0005943`	The IFSC code to get information about

Example request

1
2

curl "https://api.apiverve.com/v1/ifsclookup?ifsc=SBIN0005943" \
  -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.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — GET /v1/ifsclookup

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.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "bank": "State Bank of India",
    "ifsc": "SBIN0005943",
    "branch": "KASTURBA GANDHI MARG,NEW DELHI",
    "address": "23, HIMALAYA HOUSE KASTURBA GANDHI MARG NEW DELHI ,PIN - 110001",
    "contact": "",
    "city": "NEW DELHI",
    "district": "NEW DELHI",
    "state": "DELHI",
    "imps": true,
    "rtgs": true,
    "neft": true,
    "upi": true,
    "micr": "110002062",
    "swift": ""
  }
}

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.

Field	Type	Example	Description
`bank`	string	`"State Bank of India"`	Name of the bank institution
`ifsc`	string	`"SBIN0005943"`	IFSC code of the branch
`branch`	string	`"KASTURBA GANDHI MARG,NEW DELHI"`	Branch name and address location
`address`	string	`"23, HIMALAYA HOUSE KASTURBA GANDHI MARG NEW DELHI ,PIN - 110001"`	Street address of the branch
`contact`	string	`""`	Contact information for the branch
`city`	string	`"NEW DELHI"`	City where the branch is located
`district`	string	`"NEW DELHI"`	District of the branch location
`state`	string	`"DELHI"`	State where the branch is located
`imps`Premium	boolean	`true`	Whether IMPS transactions are supported
`rtgs`Premium	boolean	`true`	Whether RTGS transactions are supported
`neft`Premium	boolean	`true`	Whether NEFT transactions are supported
`upi`Premium	boolean	`true`	Whether UPI transactions are supported
`micr`Premium	string	`"110002062"`	MICR code for the branch
`swift`Premium	string	`""`	SWIFT code for international transactions

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.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

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

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

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.

Plan	Per month	Credits	IFSC Lookup calls	Per 1,000 calls
Free	Free	200	20	Free
Starter	$29.99	200,000	20,000	$1.50
Pro	$99.99	1,000,000	100,000	$1.00
Mega	$299.99	4,000,000	400,000	$0.75

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.

Compare all pricing tiers →

Call it from cURL — GET /v1/ifsclookup

No SDK to install — this is a plain HTTPS call to /v1/ifsclookup with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/ifsclookup" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/ifsclookup-apiSource, issues and the examples this page is built from.ReferenceIFSC Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/ifsclookupnpm APIVerve.API.IFSCLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/ifsclookup

Install the Node.js SDK, then call the IFSC Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/ifsclookup

Node.js

const res = await fetch("https://api.apiverve.com/v1/ifsclookup", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/ifsclookupThe published Node.js client, versioned and signed.GitHubapiverve/ifsclookup-apiSource, issues and the examples this page is built from.ReferenceIFSC Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.IFSCLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/ifsclookup

No SDK to install — this is a plain HTTPS call to /v1/ifsclookup with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/ifsclookup",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/ifsclookupnpm APIVerve.API.IFSCLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/ifsclookup

Install the C# / .NET SDK, then call the IFSC Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.IFSCLookup

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/ifsclookup");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.IFSCLookupThe published C# / .NET client, versioned and signed.GitHubapiverve/ifsclookup-apiSource, issues and the examples this page is built from.ReferenceIFSC Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/ifsclookupnpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/ifsclookup

No SDK to install — this is a plain HTTPS call to /v1/ifsclookup with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/ifsclookup", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/ifsclookupnpm APIVerve.API.IFSCLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/ifsclookup

No SDK to install — this is a plain HTTPS call to /v1/ifsclookup with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/ifsclookup");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/ifsclookupnpm APIVerve.API.IFSCLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/ifsclookup

No SDK to install — this is a plain HTTPS call to /v1/ifsclookup with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/ifsclookup")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/ifsclookupnpm APIVerve.API.IFSCLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Finance

View all 49 →

All articles →

Enrich Your CRM with Public Company DataAutomatically fill in company details for sales leads using SEC data. Ticker, industry, address, and more from a single API call.Read

Currency Conversion: Handling Exchange Rates CorrectlyExchange rates change constantly. Learn how to handle currency conversion in applications with accuracy and reliability.Read

Going Global: Building Multi-Currency AppsYour app works great in dollars. Now a customer in Germany wants to pay in euros. Here's what to know.Read

IFSC Lookup API

Try it — live request, no key required

About the IFSC Lookup API

What people use it for

Ways to call it

Other ways to use IFSC Lookup

Questions.

Request parameters — GET /v1/ifsclookup

Required

Authentication

Response — GET /v1/ifsclookup

Response fields

Response headers

Errors

What a call costs — 10 credits per call

Call it from cURL — GET /v1/ifsclookup

Resources

Also published for

Call it from Node.js — GET /v1/ifsclookup

Resources

Also published for

Call it from Python — GET /v1/ifsclookup

Resources

Also published for

Call it from C# / .NET — GET /v1/ifsclookup

Resources

Also published for

Call it from Go — GET /v1/ifsclookup

Resources

Also published for

Call it from PHP — GET /v1/ifsclookup

Resources

Also published for

Call it from Ruby — GET /v1/ifsclookup

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — IFSC Lookup API

Finance

Related articles

Ready to build with IFSC Lookup? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog