monzo-cli

March 24, 2026 · View on GitHub

CI

A modern CLI for Monzo Bank, rewritten in Rust

Usage

Balance

$ monzo balance

  ┌────────────────────┬───────────┐
  │                    │ Amount    │
  ├────────────────────┼───────────┤
  │ Balance            │   £490.00 │
  │ Total Balance      │ £1,250.00 │
  │ Spent Today        │   -£10.50 │
  │ Including Savings  │ £3,500.00 │
  └────────────────────┴───────────┘

Transactions

$ monzo transactions --since 7d
# Calendar range (--from / --to are aliases for --since / --before; --to is inclusive)
$ monzo transactions --from 2024-01-01 --to 2024-01-31

  ┌──────────────────┬────────────────────┬────────────┬──────────┬───────────┐
  │ Date             │ Description        │ Category   │   Amount │   Balance │
  ├──────────────────┼────────────────────┼────────────┼──────────┼───────────┤
  │ 2026-03-23 09:15 │ Pret A Manger      │ eating_out │   -£3.50 │   £490.00 │
  │ 2026-03-22 18:30 │ Tesco              │ groceries  │  -£45.20 │   £493.50 │
  │ 2026-03-22 08:00 │ TfL                │ transport  │   -£2.80 │   £538.70 │
  │ 2026-03-21 20:15 │ Netflix            │ bills      │   -£9.99 │   £541.50 │
  └──────────────────┴────────────────────┴────────────┴──────────┴───────────┘
  4 transactions

Pots

$ monzo pots

  ┌──────────────────┬───────────┬─────────────────┬──────────┬──────────┐
  │ Name             │   Balance │            Goal │ Type     │ Round-up │
  ├──────────────────┼───────────┼─────────────────┼──────────┼──────────┤
  │ Holiday Fund     │   £500.00 │ £1,000.00 (50%) │ -        │ -        │
  │ Emergency        │ £1,200.00 │               - │ -        │ -        │
  │ Coin Jar         │    £47.30 │               - │ -        │ Yes      │
  └──────────────────┴───────────┴─────────────────┴──────────┴──────────┘
  3 pots | Total: £1,747.30

Spending Insights

$ monzo insights categories --since 30d

  Spending by Category
  ┌──────────────────────┬──────────┬────────────┬─────────────────┐
  │ Category             │    Spent │ % of Total │ Bar             │
  ├──────────────────────┼──────────┼────────────┼─────────────────┤
  │ groceries            │ -£245.00 │        35% │ ████████████████│
  │ eating_out           │ -£180.50 │        26% │ █████████████   │
  │ transport            │  -£95.00 │        14% │ ███████         │
  │ bills                │  -£85.99 │        12% │ ██████          │
  │ entertainment        │  -£45.00 │         6% │ ███             │
  └──────────────────────┴──────────┴────────────┴─────────────────┘
  Total: -£651.49

$ monzo search "coffee" --since 90d
$ monzo search "Amazon" -n 50

Export

$ monzo export -f csv -o spending.csv --since 90d
$ monzo export -f json -o data.json --since 1y

JSON Mode

Every command supports --json for structured output, useful for scripting or piping into jq:

$ monzo --json balance | jq '.balance / 100'
$ monzo --json tx --since 30d -c eating_out
$ monzo --json pots

Date ranges (--from / --to)

For transactions, search, insights, and export you can bound the window with:

  • --from — same as --since: a calendar date YYYY-MM-DD (start of that day, UTC) or a relative window like 30d, 3m, 1y.
  • --to — same as --before: for a plain YYYY-MM-DD, the CLI treats it as the last day included in the range (it sets the Monzo API’s exclusive before to midnight after that day).

Example — all of January last year:

monzo insights categories --from 2024-01-01 --to 2024-01-31
monzo export -f csv -o jan-2024.csv --from 2024-01-01 --to 2024-01-31
monzo search "Tesco" --from 2024-01-01 --to 2024-01-31

On search, insights, and export, if you use --to you must also set --from (or --since). For an advanced upper bound you can still pass a full RFC3339 timestamp or a Monzo transaction id to --before; only the short YYYY-MM-DD form is rewritten as an inclusive end date.

With insights, flags can appear before or after the subcommand, e.g. monzo insights categories --from 2024-01-01 --to 2024-01-31.

All Commands

CommandDescription
balanceShow account balance, spend today, savings
transactionsList transactions with filters (category, amount, date, search)
txAlias for transactions
transaction <id>Show full transaction detail
annotate <id> <key> <value>Add metadata to a transaction
potsList pots with balances and goals
pots deposit <name> <amount>Deposit into a pot
pots withdraw <name> <amount>Withdraw from a pot
search <query>Full-text search across transactions
insightsFull spending report
insights categoriesSpending breakdown by category
insights merchantsTop merchants by total spend
insights dailyDaily spending chart
insights weeklyWeekly spending totals
insights predictMonthly projection with historical comparison
insights recurringDetect subscriptions and recurring payments
exportExport transactions to CSV or JSON
webhooksList, add, or remove webhooks
feed <title>Push a notification to your Monzo app
accountsList all accounts
developersOpen Monzo developer portal (OAuth apps) in browser
appsAlias for developers
auth loginOAuth2 login (opens browser)
auth refreshRefresh expired token
auth set-token <token>Quick setup with playground token
auth set-account <id>Set default account (acc_… from monzo accounts ID column)
auth statusCheck if token is valid

Install

cargo install monzo-cli

Or via cargo-binstall:

cargo binstall monzo-cli

Or build from source:

cargo build --release
# Binary at target/release/monzo

Setup

Monzo app approval is mandatory for OAuth
After you run monzo auth login and sign in in the browser, open the Monzo app on your phone and tap to approve the login request as soon as it appears. Until you APPROVE that prompt, Monzo may not issue a usable access token: the CLI will not work properly, and your session / connection often will not show up or update correctly on the developer portal. Do not skip this step — finish the app approval before expecting any OAuth token or API access to work.

OAuth login: approve in the Monzo app (read this)

  1. monzo auth login opens the browser; you log in to Monzo on the web.
  2. Immediately check your phone — Monzo sends a login approval request to the app.
  3. Tap approve in the Monzo app while the terminal is still waiting. If you ignore or delay this, token exchange can fail or you can end up with a half-working setup (missing account auto-detection, errors on monzo accounts, nothing visible as expected on the website).
  4. Only after approval does the CLI save tokens and continue (e.g. auto-picking a default account).
  1. Create an OAuth client in the Monzo developer apps console (or run monzo developers to open it in your browser)
  2. Set the redirect URL to http://localhost:6789/callback
  3. Run:
monzo auth login --client-id YOUR_CLIENT_ID --client-secret YOUR_CLIENT_SECRET
  1. As soon as the browser flow asks you to, complete login and approve the request in the Monzo app (see the callout and section above). Without that approval, OAuth does not fully complete and things may not work or appear on the site.

Option 2: Playground token (quick start)

Get a token from the Monzo API Playground:

monzo auth set-token YOUR_ACCESS_TOKEN

Optional: set the default account in the same step (IDs from monzo accounts, see below):

monzo auth set-token YOUR_ACCESS_TOKEN --account-id acc_00009xxxxxxxx

Default account

Monzo’s API needs an account ID on top of your access token: you can have several accounts (personal, joint, Flex, rewards, etc.), and commands like balance, transactions, and pots all use one default account stored in config.

After monzo auth login, the CLI tries to pick the first uk_retail account automatically. If that did not run (for example, you still had to approve login in the Monzo app), you may be logged in but see “No account ID configured” or similar when running other commands. Fix it without re-authenticating:

monzo accounts
monzo auth set-account acc_00009xxxxxxxx

Use the value in the ID column — it always starts with acc_. The Description column often shows a user_… ID or joint-account text; that is not an account ID. Passing a user_… value will be rejected by the CLI (and would cause API errors such as 403 if it were saved manually).

You can also set account_id in your config file (monzo config shows the path).

Caveats

  • OAuth: you must approve the login in the Monzo mobile app during monzo auth login; otherwise tokens and the developer site may not behave as expected (see Setup at the top)
  • Access tokens expire after ~6 hours. If you logged in via OAuth2, tokens are refreshed automatically when they expire - no manual action needed
  • After initial auth, you have a 5-minute window to fetch full transaction history (Monzo SCA restriction)
  • Pots with "added security" cannot be withdrawn from via the API

Contributing

I welcome and encourage all pull requests. Here are some basic rules to follow:

  1. If its a feature, bugfix, or anything please only change code to what you specify.
  2. Please keep PR titles easy to read and descriptive of changes.
  3. Pull requests must be made against main branch.
  4. Check for existing issues first, before filing an issue.
  5. Have fun!

Created & Maintained By

Cesar Ferreira (@cesarmcferreira)