Skip to main content
The BIN Continuity API is coming soon.
The Pagos BIN Continuity API provides historical lifecycle data for BIN ranges, including when they were first seen in the network source files, last seen, and their current status. You can use this API to research the history of a specific BIN, including those we’ve removed from the standard BIN file.
The BIN Continuity API returns data for all BIN ranges that have ever appeared in Pagos’ BIN database files. Calls to the standard BIN Data API only return currently active BIN ranges.

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 BIN History

You can use cURL on the command line to submit BIN Continuity 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 continuity details on BIN 41234567:
curl --request GET \
  --url 'https://parrot.prod.pagosapi.com/bins/continuity?bin=41234567' \
  --header 'Authorization: Bearer <api_key>'
This will return the lifecycle history and last known card data for the BIN:
{
  "continuity": {
    "bin": "41234567",
    "bin_min": "4123456700000000",
    "bin_max": "4123456799999999",
    "status": "active",
    "first_seen_at": "2019-03-15T00:00:00Z",
    "last_seen_at": "2024-11-01T00:00:00Z",
    "flagged_for_delete_at": null,
    "deleted_at": null,
    "days_active": 2058,
    "file_appearances": 68,
    "card": {
      "number": {
        "length": 16
      },
      "card_brand": "VISA",
      "type": "CREDIT",
      "prepaid": false,
      "product": {
        "product_id": "A",
        "product_name": "Visa Traditional"
      },
      "bank": {
        "name": "CHASE BANK USA, N.A.",
        "clean_name": "Chase"
      },
      "country": {
        "alpha2": "US",
        "numeric": "840",
        "name": "United States"
      }
    }
  },
  "correlation_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
}
If you have questions about the data returned for any given BIN, check out our BIN Data FAQ pages.

BIN Lifecycle Statuses

The status field in the response indicates where the BIN is in its lifecycle:
StatusDescription
activeBIN is currently present in the BIN file and available via the standard /bins endpoint
flagged_for_deleteBIN has been marked for deletion but is still present in the BIN file. See BIN TTL for details
deletedBIN has been removed from the BIN file and is no longer available via the standard /bins endpoint

BIN TTL (Time-To-Live)

When a BIN range is no longer present in the card network source files, Pagos doesn’t immediately remove that range from the Pagos BIN Database. Instead, we provide a grace period, tracked with the flagged_for_delete_remaining_wks field in the BIN Data API and the BIN Data Batch file. The BIN Continuity API tracks this lifecycle with the flagged_for_delete_at and deleted_at timestamps.

Use Cases

The BIN Continuity API is particularly useful for:
  • Investigating missing BINs - When a BIN that previously returned data stops appearing in the standard /bins endpoint, use /bins/continuity to understand why and when it was removed
  • Historical research - Access the last known data for a BIN range even after it has been removed from the current BIN file
  • Monitoring BIN lifecycle - Track when BINs were first added to network files, how long they’ve been active, and their deletion timeline
  • Fallback data - Use the card object as a fallback when the BIN is no longer in the active file but historical data is still valuable for your use case

BIN Continuity API Limits

The following are the API limits for BIN Continuity API calls:
BIN Continuity APIAPI EndpointAPI Limit
BIN Continuity Lookup/bins/continuity100 calls every 10 seconds

BIN Continuity API IP Addresses

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

Testing

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