TheDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/jbms/finance-dl/llms.txt
Use this file to discover all available pages before exploring further.
finance_dl.mint scraper downloads your transaction history and account balance data from Mint.com using the mintapi Python package alongside selenium and chromedriver. This page covers all configuration parameters, the output file format, deduplication behavior for merged files, a ready-to-use config example, and how to invoke the scraper from the interactive shell.
Configuration Parameters
A dictionary containing your Mint.com login credentials.
Path on the local filesystem where output files will be written. The directory will be created automatically if it does not already exist.
Path to a persistent Chrome browser profile directory. This must be a path used exclusively for this scraper configuration — do not point it at your regular browser profile. When omitted, a fresh temporary profile is created on every run.
It is highly recommended to set
profile_dir. Without it, Mint’s multi-factor authentication challenge will appear on every run, requiring manual intervention each time.A list of paths to additional CSV files containing transactions in the same column format as the
mint.csv output file. When provided, these files are merged with mint.csv and the result is written to mint-merged.csv in the output_directory. Omit this parameter entirely if you do not need merging.When
True, the scraper will not wait for all linked accounts to finish refreshing their data before downloading transactions. Set this if you want faster runs and do not need fully up-to-date balances.Output Format
The scraper writes the following files underoutput_directory:
| File | Description |
|---|---|
mint.csv | Transaction data in Mint’s standard CSV export format, excluding pending and duplicate transactions. |
mint-merged.csv | Present only when merge_files is specified. Contains the deduplicated union of mint.csv and all files listed in merge_files, sorted by date descending. |
balances.%Y-%m-%dT%H%M%S%z.csv | Timestamped snapshot of account balance data, written on each successful run. Columns: Name, Currency, Balance, Last Updated, State, Last Transaction. |
Deduplication Logic
Because the Mint CSV format has no unique transaction identifier, legitimate duplicate transactions (e.g., two identical coffee purchases on the same day at the same merchant) can produce identical rows. The merge algorithm handles this correctly: For each unique combination ofDate, Original Description, Amount, Transaction Type, and Account Name, the merged output contains N copies of that row, where N is the maximum number of times that row appears in any single input file. This means a transaction that appears twice in mint.csv and once in a merge_files entry will appear twice in mint-merged.csv.