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 BIN41234567:
If you have questions about the data returned for any given BIN, check out our BIN Data FAQ pages.
BIN Lifecycle Statuses
Thestatus field in the response indicates where the BIN is in its lifecycle:
| Status | Description |
|---|---|
active | BIN is currently present in the BIN file and available via the standard /bins endpoint |
flagged_for_delete | BIN has been marked for deletion but is still present in the BIN file. See BIN TTL for details |
deleted | BIN 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 theflagged_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
/binsendpoint, use/bins/continuityto 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
cardobject 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 API | API Endpoint | API Limit |
|---|---|---|
| BIN Continuity Lookup | /bins/continuity | 100 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.21375.2.25.63