Your bank data, one command away.
Install one binary, sign in, and pull transactions or sync feeds from your terminal. Tables for you, stable JSON for scripts and agents.
$banksync tx --bank chase --from 2026-10-01DATE DESCRIPTION AMOUNT2026-10-08 Trader Joe’s -84.202026-10-07 Uber -24.502026-10-05 Delta Air Lines -412.0042 transactions · Chase Checking ••4021$banksync feeds sync fed_123 --watch✓ Sync complete: 412 written
Install, sign in, go.
- 01
Install the CLI
One self-contained binary for macOS, Linux and Windows. No Node, no runtime.
macOS and Linux
curl -fsSL https://banksync.io/install.sh | sh# Windowsirm https://banksync.io/install.ps1 | iex
- 02
Sign in
Your browser opens to approve the CLI. Scripts and CI use an API key instead.
Terminal
banksync loginLogged in to Acme Inc (profile: default).
- 03
Run your first command
Names resolve, so --bank chase finds your Chase connection.
Terminal
banksync banks listbnk_a1b2 Chase ● activebnk_c3d4 CommBank ◐ syncing
The CLI, start to finish.
Made for scripts and agents.
Output that fits the job
$banksync tx --bank chase -o csv > october.csv$banksync tx --bank chase -o ndjson --fields date,amount{"date":"2026-10-08","amount":-84.2}{"date":"2026-10-07","amount":-24.5}$banksync tx --bank chase | jq '.data | length'42
A shell tool for your agent
$export BANKSYNC_API_KEY=bsk_live_…$banksync commands --json | jq '.commands | length'131$banksync commands --json | jq -r .api_versionv1
One key. Terminal, code or chat.
What the CLI does.
- Install
- One binary for macOS, Linux and Windows, no Node required. Installation guide
- Sign-in
- Browser OAuth with banksync login, or an API key via --api-key or BANKSYNC_API_KEY. Stored encrypted, redacted from logs.
- Commands
- Banks, accounts, transactions, balances, feeds, jobs, tables, dashboards and automations, plus banksync api for any raw endpoint.
- Output
- table, json, csv, ndjson or toon, with --fields for dot-path columns.
- Contract
- Generated from the same OpenAPI spec as the REST API. A CI gate fails the build if they drift.
- Banks
- banksync banks connect opens the web app for the bank’s own consent screen. Bank logins never touch the CLI.
- Same data
- One key and dataset with the REST API and the MCP server.
One account, three ways in.
Connected data across CLI, API and MCP
Questions, answered.
What is the BankSync CLI?
A first-party command-line tool for the BankSync API. List banks, pull transactions, manage feeds and trigger syncs from your terminal, with tables for people and stable JSON for scripts and agents.
How do I install the BankSync CLI?
Run curl -fsSL https://banksync.io/install.sh | sh on macOS or Linux, or irm https://banksync.io/install.ps1 | iex on Windows. It is one binary with no Node; then banksync login --api-key bsk_... with a key from Workspace > Developers.
Is the BankSync CLI good for AI agents?
Yes. It emits a stable JSON envelope, machine-readable errors on stderr, consistent exit codes, and a banksync commands --json catalog so an agent can discover every command, flag and field.
What output formats does the CLI support?
-o picks table, json, csv, ndjson or toon. Tables by default on a terminal, JSON when piped, and --fields selects columns with dot-paths.
How does the CLI authenticate?
banksync login opens your browser to sign in with OAuth. For scripts and CI, use an API key via banksync login --api-key or the BANKSYNC_API_KEY variable. Credentials sit in an encrypted local file and are redacted from verbose logs.
Does the CLI stay in sync with the BankSync API?
Yes. Its typed core and command reference are generated from the same OpenAPI contract as the REST API, and a CI gate fails the build if they drift.
Can I use the CLI, REST API, and MCP server together?
Yes. All three share one API key and one dataset: the CLI for scripts and agents, REST for your code, MCP for conversation.
How do I connect a bank from the CLI?
Run banksync banks connect. It opens the BankSync web app for the open-banking flow, then polls until the bank appears. Your banking credentials never touch the CLI.

