quartercall
Read QuarterCall Data — the NCUA Form 5300 Call Reports, republished as Parquet at
data.quartercall.com — into pandas. No account or API key is needed.
pip install quartercall
import quartercall
quartercall.quarters()
quarters() returns one row per published quarter, newest first:
| Column | Holds |
|---|---|
quarter |
the cycle, such as 2026Q3 |
cycle_date |
the cycle's last day |
status |
open while filings may still arrive; dormant once NCUA has validated none for over a year |
cu_count |
credit unions that have filed for the cycle |
updated_at |
when the quarter's files were last rebuilt, in UTC |
No quarter is final: NCUA accepts an amendment to a cycle of any age, and a dormant quarter
becomes open again when one arrives. A recent quarter is published while many credit unions
have yet to file.
Version 0.0.1 lists the quarters. Reading a quarter's accounts and profiles comes next.
QuarterCall is a registered trademark of QuarterCall Holdings Inc. The code is licensed under the Apache License 2.0.
Metadata
Release files for quartercall 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| quartercall-0.0.1.tar.gz | 8.5 kB | With provenance | Details for quartercall-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| quartercall-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for quartercall-0.0.1-py3-none-any.whl |
Total release size: 16.4 kB
Release files / quartercall-0.0.1.tar.gz
| Download URL | quartercall-0.0.1.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d58e3d1eac65c6aefd94fcc0fed8d75a505c136f0c0f108cbc152e65c87ba645
|
|
BLAKE2b-256 checksum How to use checksums |
b03c8a22bccc5d839c5046a0597e1ec1da81ea0ac59a59aa0966d62eba9ac978
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logRelease files / quartercall-0.0.1-py3-none-any.whl
| Download URL | quartercall-0.0.1-py3-none-any.whl |
|---|---|
| Size | 8.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a79507c3aa489dba4291ffbfa429f7f930ac81112afa11d79e69365f0786c8ab
|
|
BLAKE2b-256 checksum How to use checksums |
5ee0aefaa7f7a6de49509d8a8c1b352752392ad51a18aee959d320465d4bd40f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logSecurity for quartercall 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for quartercall-0.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.