Integrations, open banking & API
Transactions can arrive without a file and leave without a download. This page covers the connectors, live bank connections, the REST API and webhooks.
Each connector below appears under Settings → Integrations once it has been enabled for your workspace. If a connector you need is not listed there yet, ask through the contact form.
Accounting and spreadsheets
| Connector | What it does |
|---|---|
| QuickBooks Online, Xero, Sage, FreshBooks, Wave, Zoho Books | Push reconciled transactions straight into the ledger; firms map each client to its own company file |
| Odoo | The same, over Odoo's own API using your Odoo credentials |
| Google Sheets, Excel Online | Push transactions into a sheet, in batches, keeping it in step with your filters |
Before a push you see a preview: rows already synced, rows that are new, rows that still need an account mapping, and rows waiting on a transfer decision.
Watched cloud folders
Connect a folder in Google Drive (including shared drives), OneDrive or a SharePoint document library, Dropbox or Box. Statements dropped into it are uploaded and processed automatically, and count against the page allowance like any upload.
Messaging
Slack — post a notice to a channel of your choice when a statement completes or fails.
Live bank connections
On paid plans, where open banking is available for your bank, an account can be connected directly and transactions arrive without any file. Connections are managed under Accounts; a connected account shows Direct connection to the bank as its source. Availability depends on your bank and region.
REST API and webhooks
Available on Professional and Business.
- API keys are created under Settings → API keys. The secret is shown once and stored only as a hash. Each key has a read or read-write scope and its own rate limit of 120 requests a minute.
- Endpoints cover uploading statements, listing and fetching statements and transactions, exporting in any format, and reading the summary and business-summary figures. API uploads count against the same page allowance as the app.
- Webhooks deliver
statement.completedandstatement.failedevents to an HTTPS endpoint you register. Every delivery is HMAC-signed with the endpoint's secret, which is returned once at creation; an endpoint that fails twenty times in a row is disabled until you re-enable it. A sample payload for each event is available for testing.
The technical reference — request and response shapes, error codes, signature verification — lives in the developer documentation, which requires a developer sign-in.
Notifications
Alerts and statement events can reach you by email, web push and in the app. Alert rules are set under Settings; the available types are spending limit, budget warning, low balance, fraud detected, unusual activity, large transaction, duplicate transaction, recurring price change, statement processed, statement failed and quota near limit.