IFSC Lookup API
Overview
To use IFSC 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/ifsclookupExample
How to call the IFSC Lookup API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/ifsclookup?ifsc=SBIN0005943" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/ifsclookup?ifsc=SBIN0005943', {
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/ifsclookup?ifsc=SBIN0005943', 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/ifsclookup?ifsc=SBIN0005943", 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": {
"bank": "State Bank of India",
"ifsc": "SBIN0005943",
"branch": "KASTURBA GANDHI MARG,NEW DELHI",
"contact": "",
"city": "NEW DELHI",
"district": "NEW DELHI",
"state": "DELHI",
"imps": true,
"rtgs": true,
"neft": true,
"upi": true,
"micr": "110002062",
"swift": ""
}
}Authentication
The IFSC 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 IFSC Lookup API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the IFSC Lookup API:
Get IFSC Code Information
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
ifsc | string | required | The IFSC code to get information about | - |
Response
The IFSC 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>
<bank>State Bank of India</bank>
<ifsc>SBIN0005943</ifsc>
<branch>KASTURBA GANDHI MARG,NEW DELHI</branch>
<contact></contact>
<city>NEW DELHI</city>
<district>NEW DELHI</district>
<state>DELHI</state>
<imps>true</imps>
<rtgs>true</rtgs>
<neft>true</neft>
<upi>true</upi>
<micr>110002062</micr>
<swift></swift>
</data>
</response>
status: ok
error: null
data:
bank: State Bank of India
ifsc: SBIN0005943
branch: KASTURBA GANDHI MARG,NEW DELHI
contact: ''
city: NEW DELHI
district: NEW DELHI
state: DELHI
imps: true
rtgs: true
neft: true
upi: true
micr: '110002062'
swift: ''
| key | value |
|---|---|
| bank | State Bank of India |
| ifsc | SBIN0005943 |
| branch | KASTURBA GANDHI MARG,NEW DELHI |
| contact | |
| city | NEW DELHI |
| district | NEW DELHI |
| state | DELHI |
| imps | true |
| rtgs | true |
| neft | true |
| upi | true |
| micr | 110002062 |
| swift |
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 |
|---|---|---|---|
bank | string | Name of the bank institution | |
ifsc | string | IFSC code of the branch | |
branch | string | Branch name and address location | |
contact | string | Contact information for the branch | |
city | string | City where the branch is located | |
district | string | District of the branch location | |
state | string | State where the branch is located | |
impsPremium | boolean | Whether IMPS transactions are supported | |
rtgsPremium | boolean | Whether RTGS transactions are supported | |
neftPremium | boolean | Whether NEFT transactions are supported | |
upiPremium | boolean | Whether UPI transactions are supported | |
micrPremium | string | MICR code for the branch | |
swiftPremium | string | SWIFT code for international transactions |
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 IFSC Lookup through GraphQL to combine it with other API calls in a single request. Query only the ifsc 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 {
ifsclookup(
input: {
ifsc: "SBIN0005943"
}
) {
bank
ifsc
branch
contact
city
district
state
imps
rtgs
neft
upi
micr
swift
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The IFSC 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
IFSC 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 IFSC 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 IFSC Lookup
Official IFSC Lookup packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
IFSC 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 IFSC Lookup?
How many credits does IFSC Lookup cost?
Each successful IFSC 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 ifsc lookup lookups.
Can I use IFSC Lookup in production?
The free plan is for testing and development only. For production use of IFSC 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 IFSC Lookup from a browser?
What happens if I exceed my IFSC Lookup credit limit?
When you reach your monthly credit limit, IFSC 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.








