Build on 2Fin

2Fin is built to be extended. Push transactions and expenses in, send signed webhooks out, connect any assistant through MCP, bring your own bank feed, invoicing tool and model, and run it on your own machine if you like — all of it documented.

The building blocks

In, out and conversational: an API to bring records in, webhooks to act on them, and an MCP server that turns your own records into something an assistant can work with. Each one opens its page in the docs.

Bring your own

2Fin sits among the tools you already use rather than replacing them, so nothing has to be migrated and nothing is locked in. When you want to move, your transactions leave as a CSV.

Shape how Fin thinks

Fin’s automatic categorising learns from every correction, and you can steer it directly: rules start on Premium, and category sets and Lenses are on ELITE+. How Fin decides.

Rules that sort for you

Write a rule once — this merchant, this category, this tax treatment — and every matching transaction follows it, imported or live.

Category sets of your own

Build the categories your work actually uses, keep more than one set, and switch between them on ELITE+.

Lenses

Read the same transactions by tax year, project, client or property without re-tagging them, with more than one lens at once.

Tax treatment per category

Set the GST or VAT treatment on each category and override it on any transaction, with the working shown.

Run it where you want

Use the web app in any browser, install the Windows desktop app and keep your records in a folder you own, or self-host with Docker Compose or one CloudFormation stack in your own AWS account. Self-hosting 2Fin and the desktop app.

Developers, answered

Questions about building on 2Fin

Does 2Fin have an API?
Yes. The Integrations API pushes transactions and expenses in, signed webhooks send events out, and the MCP server lets an assistant read your records and, with the permission you approve, change them. The API reference and an OpenAPI file are at docs.ai2fin.com.
Can 2Fin talk to Zapier, Make or n8n?
Both ways. Point a signed webhook at a Zapier, Make or n8n hook to act the moment a transaction is categorised, an expense is created or a receipt is processed, and push records back in through the Integrations API with an idempotency key so a retry never doubles them. Webhooks are on AUTO+.
Which plan includes the developer features?
API keys and the MCP server are on every plan, including Free, and what an assistant can read follows your plan. Custom rules start on Premium; your own category sets, Lenses, the four destinations and the Xero and QuickBooks Online push are on ELITE+; signed webhooks and scheduled email reports are on AUTO+.
Can I use my own bank feed and my own model?
Yes. Connect a bank feed with a key you own — SimpleFIN or BankSync — or bring statements in as CSV, Excel, PDF, OFX, QFX, QIF, CAMT.053 or MT940 files, or from a spreadsheet feed. On the desktop app, Fin can run on your own Anthropic, OpenAI or AWS Bedrock key, or on a local model such as Ollama or LM Studio.
Where are the developer docs?
At docs.ai2fin.com: a quick start, the REST API reference with its OpenAPI file, the MCP guides and tool catalogue, the webhook events and signature headers, the bank-feed connectors and the deployment options for cloud, desktop and self-hosted.

Start free, then build what you need.

API keys and the MCP server are on the free plan, and the docs are open to everyone.