Diversified Banks Data Provider · Head-to-head
FDIC BankFind Suite API vs SEC EDGAR XBRL Financial Statements API
Which diversified banks data provider data fits your job: FDIC BankFind Suite API, or SEC EDGAR XBRL Financial Statements API. API, files, or your warehouse. Daily, weekly, or hourly.
FDIC BankFind Suite API
SEC EDGAR XBRL Financial Statements API
Coverage, side by side
| FDIC BankFind Suite API | SEC EDGAR XBRL Financial Statements API | |
|---|---|---|
| Geographic | United States - all states, DC and territories; the location file reaches down to individual domestic offices | All SEC-registered issuers, US-listed including foreign private issuers |
| Temporal | Registry current as of the latest update; quarterly financials running back decades (JPMorgan records begin March 1984); 4,115 historical failures | Full XBRL history per company; JPMorgan Chase facts verified back to 2008, with a filings index alongside |
| Granularity | Per institution, per branch or office, quarterly for financial data | Per company, per XBRL concept, per reporting period |
What each contains
Pick by fit, not by loyalty.
| FDIC BankFind Suite API | SEC EDGAR XBRL Financial Statements API | |
|---|---|---|
| Geography | United States - all states, DC and territories; the location file reaches down to individual domestic offices | All SEC-registered issuers, US-listed including foreign private issuers |
| Temporal reach | Registry current as of the latest update; quarterly financials running back decades (JPMorgan records begin March 1984); 4,115 historical failures | Full XBRL history per company; JPMorgan Chase facts verified back to 2008, with a filings index alongside |
| Granularity | Per institution, per branch or office, quarterly for financial data | Per company, per XBRL concept, per reporting period |
| Unit of analysis | The insured bank subsidiary - certificate number and Federal Reserve ID on every row | The public registrant - CIK-numbered holding companies and operating issuers alike |
| Scale | ~4,700 active institutions, ~4,100 failure records, millions of quarterly financial rows | Millions of filings; a single large-bank company facts file runs 8 MB across 900-plus concepts |
| Field dictionary | ~150 documented fields per institution record, definitions published as property files | Fact-level fields for identifier, taxonomy, tag, label, units, period, value, form and dates |
Or take both in one feed
They stack into the classic top-down-plus-bottom-up bank workflow, joined by nothing fancier than a mapping table. Screen the whole industry through the FDIC registry - size bands, charter classes, states, deposit growth - then open the EDGAR XBRL books for the subset that files, pulling Deposits and NetIncomeLoss histories to check whether the supervisory ratios survive contact with as-reported statements. An M&A team can trace acquisition chains in the structure-change events while valuing targets from filed financials; a credit researcher can benchmark a community lender against listed peers even though only half of that comparison exists in filings.
Two practical notes from the records. Map CERT to CIK deliberately - the names differ ('National Association' on one side, holding-company style on the other) and mergers leave stale pairs behind. And mind the calendar: one side stamps quarters as YYYYMMDD report dates, the other as fiscal-period ends. Or take both in one feed.
API, files, or your warehouse. Daily, weekly, or hourly.
Fair questions
Which one should a bank credit analyst sample first?
Sample both, pick by fit. Analysts covering the whole industry start with the FDIC registry for universe, deposits and failure context; analysts writing credit opinions on listed banks start with EDGAR XBRL for as-filed GAAP detail and filing-level provenance. Teams doing surveillance across public and private lenders keep both in rotation.