parsimony-bde
Banco de España connector — Spanish macroeconomic, monetary, and financial time series via the BIEST REST API.
Part of the parsimony-connectors monorepo. Distributed standalone on PyPI as parsimony-bde.
Connectors
| Name | Kind | Description |
|---|---|---|
bde_fetch |
connector | Fetch one or more BdE time series by series code (comma-separated). |
enumerate_bde |
enumerator | Discover BdE series from six catalog CSV chapters plus the Bank Lending Survey (recovered from pb.zip). |
bde_search |
connector | Semantic-search the published BdE catalog snapshot; returns ranked series codes. |
bde_fetch's time_range is frequency-dependent (BdE validates it): monthly /
quarterly series take 30M/60M/MAX, daily series take 3M/12M/36M (not
MAX), and any frequency accepts a 4-digit year (e.g. 2024). A range that
doesn't fit a series' frequency is reported as an InvalidParameterError.
Install
pip install parsimony-bde
Pulls in a compatible parsimony automatically. Verify discovery:
python -c "from parsimony import discover; print([p.name for p in discover.iter_providers()])"
Configuration
No API key required — the BdE BIEST API is open and unauthenticated.
bde_search reads a published catalog snapshot (default hf://parsimony-dev/bde).
Override the snapshot location with the PARSIMONY_BDE_CATALOG_URL environment
variable, or pass catalog_url= at call time.
Quick start
from parsimony_bde import CONNECTORS
result = CONNECTORS["bde_fetch"](key="D_1NBAF472")
print(result.raw.head())
For multi-plugin composition (autoloads everything installed):
from parsimony import discover
connectors = discover.load_all()
Catalogs
enumerate_bde discovers the full BdE series catalog — ~15.5k unique series
across six published CSV chapters (be, cf, ie, si, tc, ti), plus the
Bank Lending Survey. The survey's CSV chapter lists only un-fetchable family
aliases (PB_1_1.1), so its real fetchable codes (DPB…) are recovered from the
bulk pb.zip. Rows are de-duplicated by series code (a series can appear under
more than one thematic chapter). Maintainers build a Catalog snapshot from the
enumerator (see scripts/build_catalog.py) and push it to the snapshot URL that
bde_search reads. The crawl is expensive (the CF/Financial-Accounts chapter
alone is several thousand series), so it runs offline as a publish job — never at
query time.
A small tail (~1% of catalog codes, mostly dollar-denominated …$… financial
accounts variants and a handful of external-sector series) is listed in the CSV
catalog but not served by the web service; fetching such a code returns a clear
InvalidParameterError rather than data.
Provider
- Homepage: https://www.bde.es
- API docs: https://www.bde.es/webbe/en/estadisticas/recursos/api-estadisticas-bde.html
- Series browser: https://app.bde.es/bie_www/bie_wwwias/xml/Arranque.html (BIEST)
License
See LICENSE.
Metadata
Release files for parsimony-bde 0.0.2
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 | |
|---|---|---|---|---|
| parsimony_bde-0.0.2.tar.gz | 17.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| parsimony_bde-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.3 kB
Release files / parsimony_bde-0.0.2.tar.gz
| Download URL | parsimony_bde-0.0.2.tar.gz |
|---|---|
| Size | 17.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d2ba6a9a1c82c50b0e42e3466a2ce35517baf28e3eb0abf70e3a7f47ce7d0c5c
|
|
BLAKE2b-256 checksum How to use checksums |
eae12f52470c5f1ec46b8ff00793d1dca1367da7fe9f4515282864d27e743d77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Aug 10, 2026.
Transparency logRelease files / parsimony_bde-0.0.2-py3-none-any.whl
| Download URL | parsimony_bde-0.0.2-py3-none-any.whl |
|---|---|
| Size | 19.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e80841478e80c15109ff5cdec022e610ae600b75f5afa61f6f8c2c2b3c49e109
|
|
BLAKE2b-256 checksum How to use checksums |
6563be3d85297ca2fb5f6be8d82a82e62417d3821b33bae982d6296e73003a95
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Aug 10, 2026.
Transparency logSecurity for parsimony-bde 0.0.2
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 parsimony_bde-0.0.2.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 Aug 10, 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.