IFSC Lookup API

About the IFSC Lookup API

Use it as an IFSC code checker in payout and onboarding flows, or as a bulk IFSC code search that checks a list of codes one call per row from a script or spreadsheet. Pass any valid 11-character IFSC code to get the branch it belongs to: institution name, branch, address, contact number, city, district, state and clearing centre. Records come from the open IFSC dataset compiled from RBI and NPCI publications, and a code missing from our copy is checked against the live public source. Paid plans also return MICR, SWIFT codes, and payment rail flags for 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.

Bulk IFSC Verification

Run a spreadsheet or CSV of IFSC codes through the API one row at a time to flag codes that no longer resolve and fill in the bank and branch for the rest.

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 IFSC Lookup against — what each one is better at, in plain terms.

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

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.

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.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

{
  "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": "",
    "centre": "NEW DELHI",
    "iso3166": "IN-DL",
    "bankcode": "SBIN",
    "branchcode": "005943"
  }
}

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 IFSC 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 — IFSC 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