Your unofficial guide to US Bank Regulatory Data

Call.Report:
libraries, documentation, and examples

Call.Report is a working reference for the FFIEC Call Report, UBPR, and the ffiec-data-connect Python library, in addition to other tools and resources for working with US bank regulatory data.

Quickstart → Libraries

python Fetch one bank's Call Report examples/01_quickstart.ipynb

from ffiec_data_connect import OAuth2Credentials, collect_data

creds = OAuth2Credentials(
    username="your_cdr_username",
    bearer_token="eyJhbGci...",  # 90-day JWT from the FFIEC portal
)

# RSSD 480228 = JPMorgan Chase Bank, N.A.
data = collect_data(
    creds,
    rssd_id="480228",
    reporting_period="12/31/2025",
    series="call",
    output_type="pandas",
    force_null_types="pandas",   # keep integers as integers
)

That's the entire pattern. One credentials object, one function call per institution. Identifiers render in monospace — like this 480228 — throughout the site.

Libraries

ffiec-data-connect (Python)

The Python library — install, auth, quickstart, function reference, output formats, bulk pulls, async, troubleshooting, migration from v2. Everything ffiec-data-connect in one place.

Docs

General FFIEC concepts

Library-agnostic reference material. Small today — most practical content lives under Libraries. Reserved for reporting cycles, XBRL basics, and identifier systems.

Data Sources

What the data is

Call Reports, UBPR, NIC attributes, bulk files, and how to join across FFIEC, Fed, FDIC, OCC identifiers.

Data

Downloadable catalogs

Machine-readable extracts built on top of FFIEC primary sources — the 29,908-field MDRM + UBPR catalog in JSONL today, more to come. Periodically refreshed, MPL-2.0.

Why this exists

US bank regulatory data is powerful and nearly public — every insured depository institution files quarterly, and every filing is online — but working with it is painful. Identifiers are cryptic (RCON2170, RSSD, FDIC cert, FFIEC 041 Schedule RC-R Part II), the data spans five regulators and multiple report populations, documentation lives in PDFs, and what little open-source tooling exists is often wrong at the first line of an example.

You'll find a Python client (ffiec-data-connect) for pulling Call Report and UBPR data, pages explaining each report, a JSONL catalog of every public FFIEC field, and an interactive API reference for anyone not using Python. Code examples come from the library's own test suite and example notebooks — if they don't work against the real API, it's a bug.

Support the work

Keep this open and current.

Call.Report and ffiec-data-connect are independent, free, and MPL-2.0 / CC BY 4.0 licensed. Sponsorships fund the time spent tracking FFIEC API changes, updating docs against restatements, and keeping the library correct for everyone.

Other ways to help →