starling-beancount
What is this
Use a Starling Developer account to programatically export your bank transactions to beancount files.
There are two main scripts:
- starling_beancount/extractor.py converts Starling API JSON to beancount Transactions and Balances.
- starling_beancount/importer.py contains the configuration for
bean-extractto parse that.
Setup
Get a Starling Personal Access Token with the following scopes:
account:read
balance:read
transaction:read
space:read
Save the provided token text in a file somewhere useful (near your beancount files probably).
Install this library:
pip install starling-beancount smart_importer
Configuration
Make a copy of config.yml and edit it to suit your needs.
- The
jointAccsanduserIdsfields are only needed if you have a joint account and you want to add metadata about which user made a transaction.
💪 Running the script
Then run the script:
Usage: starling [OPTIONS] ACC
Options:
--fr TEXT
--to TEXT [default: today]
--balance / --no-balance [default: no-balance]
Example to get the transactions from assets_starling (or whatever you called your token file) from a date until today:
starling assets_starling --fr=2021-01-01
Print the balance:
starling assets_starling --balance
🧠 As a beancount importer
You will need to add something like the following to your bean-extract configuration (eg config.py):
from starling_beancount.importer import StarlingImporter
from smart_importer import apply_hooks, PredictPostings
from smart_importer.detector import DuplicateDetector
CONFIG = [
...,
apply_hooks(StarlingImporter(
config_path="path/to/config.yml",
acc="assets_starling",
token_path="path/to/token.txt",
bean_path="path/to/ledger.bean",
), [DuplicateDetector(), PredictPostings()])
]
Then add a Note to your ledger, specifying the earliest date you would like starling-beancount to extract from.
It must have the text "bean-extract" somewhere in it.
A new note will be added each time you run the script, so that you don't have to deal with too many duplicates.
2022-03-01 note Assets:Starling "bean-extract"
Last thing! You must create the "target" file that bean-extract will look for.
Since we don't actually need a file (it all comes from the API), just add a file to wherever you would normally place them.
👉 Make sure to name this the same as the acc= argument to StarlingImporter above.
touch ./raw/assets_starling
So long as this file is there, bean-extract (and, by extension, the Fava importing tool) will find it and offer you to import that account.
Then run the following:
bean-extract config.py raw/assets_starling
Prior art
jorgeml/starlingbank does a similar thing, albeit more simply (probably for the better).
Metadata
Release files for starling-beancount 2.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| starling_beancount-2.1.0.tar.gz | 6.7 kB | Details |
Release files / starling_beancount-2.1.0.tar.gz
| Download URL | starling_beancount-2.1.0.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8c406ea20757bd3ab54376ae416ea0ff89c4f11607b59367698252328c59bb19
|
|
BLAKE2b-256 checksum How to use checksums |
77b677a6b6c4b3c5f6c066847484fa10e40214a126f6f12353284475e1f609ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 28, 2026.
Transparency log