Skip to main content
The Pagos BIN Data API is a very simple REST API that expects to receive—as input—a 6-10 digit BIN/IIN, and returns a simple JSON object back containing known details for the BIN.
If you prefer to query BIN data through your AI tools, check out our guide on the Pagos MCP Server

​
Authentication

The Pagos platform uses API keys to authenticate requests to all our services. See our API Authentication guide for full instructions on generating API keys and authenticating with the Pagos APIs.

​
Look Up a BIN

You can use cURL on the command line to submit BIN Data API requests, but you can also use API query tools like Postman or integrate the API direclty into your systems. Here’s a cURL example for details on BIN 55630400 
curl --request GET \
  --url 'https://parrot.prod.pagosapi.com/bins?bin=55630400' \
  --header 'Authorization:Bearer <api_key>'
This will return the details for the BIN: 
{
  "card": {
    "number": {
      "length": 16
    },
    "bin_min": "5563040000000000000",
    "bin_max": "5563049999999999999",
    "card_brand": "MASTERCARD",
    "type": "Credit",
    "prepaid": false,
    "product": {
      "product_id": "MCF",
      "product_name": "Mastercard Corporate Fleet Card"
    },
    "bank": {
      "name": "CITIBANK N.A."
    },
    "country": {
      "alpha2": "US",
      "numeric": "840",
      "name": "UNITED STATES OF AMERICA"
    },
    "correlation_id": "eyJGaWxlSWQiOjI3NiwiVmVyc2lvbiI6NX0="
  }
}
If you have questions about the data returned for any given BIN, check out our BIN Data FAQ pages.

​
Enhanced Data

With the BIN Data API, you can request enhanced data by including the query paramater enhanced=true on you request. This provides you with up to 35 additional fields beyond the standard data fields. It includes additional card brand information, estimated interchange costs, SCA regulation requirements, and more. See the BIN Data API Dictionary for a detailed list of the enhanced data fields available and an example of how BIN data appears in a query response. For example: 
curl --request GET \
  --url 'https://parrot.prod.pagosapi.com/bins?bin=55630400&enhanced=true' \
  --header 'Authorization:Bearer <api_key>'

​
BIN TTL (Time-To-Live)

When a BIN range no longer appears in the card network source files, Pagos doesn’t immediately remove that range from the API response. Instead, we provide a grace period using the flagged_for_delete_remaining_wks field. For each BIN range, the value in this field will be either:
  • Null - The BIN range is active and not flagged for deletion
  • An integer 1-4 - The number of weeks until this BIN range is officially removed from the BIN snapshot database
The first week our network source files no longer contain a particular BIN range, we’ll populate this field with a 4. Each subsequent week the BIN range remains absent, this value decreases by 1; by the fifth week, we remove the range entirely from the BIN snapshot database. If a network adds back a BIN range previously flagged for deletion, a null response replaces the countdown. This feature helps you:
  • Plan for upcoming BIN removals before they affect your systemsß
  • Maintain continuity when network files temporarily omit a BIN range due to errors
  • Distinguish between permanent BIN removals and temporary network file issues
To research BIN history or access data for BIN ranges that have been removed, see the BIN Continuity API.

​
Brands Covered

At this time, the BIN Data API includes data for the following card brands.
  • PayPal
  • Discover
  • Prop
  • JCB
  • Mastercard
  • Visa
  • Amex
  • Elo
  • EBT
  • Dankort
  • Diners Club
  • Unionpay
  • EFTPOS Australia
  • RuPay
  • Accel
  • NYCE
  • STAR
  • PULSE
  • Korean Local
  • MIR
  • Culiance
  • Bancontact
  • Carte Bancaire
  • Hipercard
  • ATM Card
  • UATP
  • Cirrus
  • Private Label
  • Maestro

​
Card Product ID and Name

When available, we will provide the details around the card product ID and the card product name – this will denote the type of card typically present on the BIN. More details are available in the BIN / IIN Product Code Guide.

​
BIN Data API Limits

The following are the API limits for BIN Data API calls:
BIN Data APIAPI EndpointAPI Limit
Single BIN Lookup/bins100 calls every 10 seconds
Multiple BIN Lookup (50 BINs per API call)/bins/multiple6 calls every 10 seconds

​
BIN Data API IP Addresses

The following static IP addresses can be used to allowlist API traffic to the Pagos BIN Data API:
  • 99.83.189.213
  • 75.2.25.63

​
Testing

You can explore the Pagos BIN Data API in sandbox by enabling Test Mode and following the testing details.