filings-b3 
Biblioteca Python simples e eficiente para acessar os conjuntos de dados públicos da B3 (a bolsa
brasileira). Cada reader transforma um pregão em um pandas.DataFrame tipado, validado por
contrato e com proveniência — valores monetários como Decimal exato, nunca um float com perda.
✨ Principais recursos
📊 Readers do Boletim Diário (BDI)
BdiStocksSummaryReader— o resumo por pregão do mercado à vista de ações (DailyAverageStocks).BdiBtbLendingOpenPositionsReader— o retrato das posições em aberto de empréstimo de ativos (BTB) (BTBLendingOpenPosition).
🔒 Fidelidade por construção
- Tipagem explícita — toda coluna tipada na carga, nunca a inferência do pandas.
- Decimais exatos — dinheiro e qualquer valor cuja parte fracionária importa é
decimal.Decimal, nunca umfloatbinário. - Contratos — uma fonte que remove uma coluna obrigatória falha de forma barulhenta com
ContractError, verificado contra os layouts publicados pela própria B3.
🧾 Proveniência & camada bronze
- Seis colunas de proveniência em todo frame (
url,updated_at,source_key,package_version,ingestion_run_id,content_hash). - Passe
path_raw=para reter cada página bruta da fonte para a camada bronze de um datalake.
🚀 Primeiros passos
Pré-requisitos
- Python 3.10+
- Poetry (recomendado)
- Opcional: Makefile
Instalação
Opção 1: Pip (recomendado)
pip install filings-b3
Opção 2: Build a partir do código-fonte
git clone https://github.com/guilhermegor/filings-b3.git
cd filings-b3
pyenv install 3.12.2
pyenv local 3.12.2
poetry install --no-root
poetry shell
Uso básico
from datetime import date
from filings_b3.daily_bulletin import BdiBtbLendingOpenPositionsReader
df = BdiBtbLendingOpenPositionsReader(date(2025, 1, 2)).read()
print(df[["TCKR_SYMB", "STOCK_BALANCE", "BALANCE"]].head())
Importar pela macro-seção (filings_b3.daily_bulletin) é a forma organizada e preferida; a
reexportação plana a partir da raiz (from filings_b3 import BdiBtbLendingOpenPositionsReader)
continua válida por retrocompatibilidade.
date_ref é obrigatório — o endpoint do BDI é endereçado por data, então não existe um padrão
"mais recente". Veja a documentação para cada reader
e mais receitas.
Rodando os testes
poetry run pytest tests/unit/ -v
poetry run pytest tests/integration/ -v
📂 Estrutura do projeto
filings-b3/
├── .github/
│ ├── workflows/
│ ├── CODEOWNERS
│ └── PULL_REQUEST_TEMPLATE.md
├── assets/
│ └── b3-logo.png
├── bin/
├── docs/
├── src/filings_b3/
│ ├── daily_bulletin/ # readers do Boletim Diário do Pregão (BDI)
│ ├── search_trading_session/ # readers da Pesquisa por Pregão
│ └── _internal/ # privado: contracts, utils, ports
├── tests/
│ ├── unit/
│ ├── integration/
│ └── performance/
├── LICENSE
├── Makefile
├── poetry.lock
├── pyproject.toml
├── README.md
└── requirements.txt
👨💻 Autores
📜 Licença
Este projeto é licenciado sob a Licença MIT — veja LICENSE.
🔗 Links úteis
Metadata
Release files for opendata-b3 0.1.4
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 |
|---|---|---|---|---|
| opendata_b3-0.1.4.tar.gz | 65.5 kB | With provenance | Details for opendata_b3-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| opendata_b3-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for opendata_b3-0.1.4-py3-none-any.whl |
Total release size: 156.6 kB
Release files / opendata_b3-0.1.4.tar.gz
| Download URL | opendata_b3-0.1.4.tar.gz |
|---|---|
| Size | 65.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f5cc1448763bfdbaa49c0632475eacc7d339ded722703a54df744674913613da
|
|
BLAKE2b-256 checksum How to use checksums |
824cbade9ec9953bb0bde8e586f2493705b8e7568cd4146c2f0044693de2fa2d
|
| 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 Nov 11, 2026.
Transparency logRelease files / opendata_b3-0.1.4-py3-none-any.whl
| Download URL | opendata_b3-0.1.4-py3-none-any.whl |
|---|---|
| Size | 91.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ef734301c0be04a256d0389c415e043476517d1e5017c718e90e0c857bfcf8a8
|
|
BLAKE2b-256 checksum How to use checksums |
bc2a1c5b50b14259ce0f568e7f91001af3f503a7ce62178280e3eefe171025ae
|
| 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 Nov 11, 2026.
Transparency logSecurity for opendata-b3 0.1.4
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
Both files in this release have been uploaded with provenance metadata.
Attestation for opendata_b3-0.1.4.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 Nov 11, 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.