BIN Lookup API
Overview
To use BIN 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/binlookupExample
How to call the BIN Lookup API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/binlookup?bin=448590" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/binlookup?bin=448590', {
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/binlookup?bin=448590', 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/binlookup?bin=448590", 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": {
"bin": "448590",
"brand": "VISA",
"type": "CREDIT",
"category": "PURCHASING",
"country": "United States",
"issuer": {
"name": "JPMORGAN CHASE BANK, N.A.",
"country": "United States",
"phone": "1-800-432-3117",
"website": "www.chase.com"
},
"location": {
"latitude": "37.0902",
"longitude": "-95.7129",
"alpha2": "US",
"alpha3": "USA"
}
}
}Authentication
The BIN 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 BIN Lookup API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the BIN Lookup API:
Lookup Credit Card Information
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
bin | string | required | The first six digits of the credit card number (BIN) Length: 6 - 8 chars | - |
Response
The BIN 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>
<bin>448590</bin>
<brand>VISA</brand>
<type>CREDIT</type>
<category>PURCHASING</category>
<country>United States</country>
<issuer>
<name>JPMORGAN CHASE BANK, N.A.</name>
<country>United States</country>
<phone>1-800-432-3117</phone>
<website>www.chase.com</website>
</issuer>
<location>
<latitude>37.0902</latitude>
<longitude>-95.7129</longitude>
<alpha2>US</alpha2>
<alpha3>USA</alpha3>
</location>
</data>
</response>
status: ok
error: null
data:
bin: '448590'
brand: VISA
type: CREDIT
category: PURCHASING
country: United States
issuer:
name: JPMORGAN CHASE BANK, N.A.
country: United States
phone: 1-800-432-3117
website: www.chase.com
location:
latitude: '37.0902'
longitude: '-95.7129'
alpha2: US
alpha3: USA
| key | value |
|---|---|
| bin | 448590 |
| brand | VISA |
| type | CREDIT |
| category | PURCHASING |
| country | United States |
| issuer | {name:JPMORGAN CHASE BANK, N.A.,country:United States,phone:1-800-432-3117,website:www.chase.com} |
| location | {latitude:37.0902,longitude:-95.7129,alpha2:US,alpha3:USA} |
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 |
|---|---|---|---|
bin | string | The BIN number provided in the request | |
brand | string | Card brand (VISA, Mastercard, American Express, etc.) | |
type | string | Card type (CREDIT, DEBIT, PREPAID, etc.) | |
categoryPremium | string | Card category (PURCHASING, TRAVEL, etc.) | |
country | string | Country where card was issued | |
issuer | object | - | |
â”” name | string | Full name of the issuing bank | |
â”” countryPremium | string | Country where issuer is located | |
â”” phonePremium | string | Contact phone number of the issuer | |
â”” websitePremium | string | Official website URL of the issuer | |
location | object | - | |
â”” latitudePremium | string | Latitude coordinate of issuer location | |
â”” longitudePremium | string | Longitude coordinate of issuer location | |
â”” alpha2Premium | string | Two-letter ISO country code of location | |
â”” alpha3Premium | string | Three-letter ISO country code of location |
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 BIN Lookup through GraphQL to combine it with other API calls in a single request. Query only the bin 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 {
binlookup(
input: {
bin: "448590"
}
) {
bin
brand
type
category
country
issuer {
name
country
phone
website
}
location {
latitude
longitude
alpha2
alpha3
}
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The BIN 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
BIN 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 BIN 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 BIN Lookup
Official BIN Lookup packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
BIN 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 BIN Lookup?
How many credits does BIN Lookup cost?
Each successful BIN 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 bin lookup lookups.
Can I use BIN Lookup in production?
The free plan is for testing and development only. For production use of BIN 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 BIN Lookup from a browser?
What happens if I exceed my BIN Lookup credit limit?
When you reach your monthly credit limit, BIN 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.








