Skip to main content
Changes that affect callers of the API, grouped by month, newest first. Changes that only affect the app’s screens are not listed. How changes are made and announced is described in Versioning and deprecation.

November 2026

  • Data history and undo. New GET /api/data-history lists what changed in your books (imports, review batches, assistant changes, rule runs, deleted imports, edits), with cursor paging through before and limit. GET /api/data-history/change-sets/{id} previews an undo without changing anything, and POST /api/data-history/change-sets/{id}/undo performs it. Batches can be undone for 30 days.
  • Transaction list paging. GET /api/bank/transactions now reaches every page of a long history. pagination.total is the real count; it was previously capped at 1,500.
  • Rule order. POST /api/custom-rules/reorder sets the order your rules run in.
  • Imports. Uploading a second export with the same file name is no longer refused, and overlapping bank exports import each transaction once.
  • Ownership checks. Requests that reference a record belonging to another account, such as a category id, are refused instead of being accepted silently.

October 2026

  • Agent discovery. https://api.ai2fin.com/.well-known/oauth-protected-resource now names the origin as a resource (RFC 9728), /mcp answers unauthenticated calls with a 401 and a WWW-Authenticate challenge pointing at its metadata, and the server publishes an MCP Server Card and agent sign-up instructions.
  • Change sets. GET /api/change-sets/{id} and POST /api/change-sets/{id}/undo undo a batch of edits made by the assistant or an import.
  • Import review. GET /api/bank/import-review/open lists imports that are not finished yet.
  • Cash-flow forecast. New MCP tool get_cash_flow_forecast, including what-if tests.
  • Single transaction. GET /api/bank/transactions/{id} returns one transaction.
  • Integration API: banking standards. POST /api/integrations/v1/transactions accepts batches of up to 500 in ISO 20022 canonical form, FDX, CDS (Australia), Open Banking UK v4, Berlin Group or SimpleFIN (format). New POST /api/integrations/v1/statements imports CAMT.053, CAMT.054, MT940 and OFX files. Card numbers in text fields are masked before anything is stored.
  • Integration API: partner sandboxes. Partners can try the Integration API against a sandbox account with synthetic data; GET /api/integrations/v1/me reports sandbox: true for one.
  • OAuth. Pushed authorization requests (/api/oauth/par), the iss authorization response parameter (RFC 9207) and DPoP-bound tokens are available to every client; private_key_jwt client authentication is available for partner clients where enabled. Refresh tokens now rotate on every use.
  • Assets. POST /api/assets/import imports an asset register from CSV or Excel.
  • Bank feeds on outbound surfaces. Transactions from connected bank feeds are now included in MCP results and webhook payloads, marked source: "bank_feed" on webhooks.
  • Scopes for registered clients. Clients registered through Dynamic Client Registration can be granted the write scopes the person approves.
  • MCP. A read-only consent option, duplicate-safe write tools, published per-tool rate limits and tool documentation.
  • Chat. POST /api/chat/report reports a problem with an assistant answer.

September 2026

  • Upcoming money. New GET /api/upcoming and GET /api/upcoming/needs-a-look; GET /api/bank/transactions can merge upcoming rows (includeUpcoming). New MCP tool get_upcoming_money.
  • Expected income. MCP tools for money you are waiting for.
  • Split transactions. New /api/splits routes; GET /api/bank/transactions?includeSplits=1 returns each row’s split lines; MCP transaction and bill tools read and set splits.
  • Properties. MCP tools query_places and manage_place, and the property on every write tool.
  • Preferences. PUT /api/country/preferences returns only the preferences, not the whole account record.

August 2026 (from 15 August)

  • Asset register. MCP tools query_assets and manage_asset.
  • Default OAuth scope. An authorization request with no scope now gets the full MCP set (read:transactions write:transactions read:bills write:bills), each listed on the consent screen, instead of read-only.
  • Webhooks plan check. The Integration API webhook endpoints now require the Auto+ plan, the same as webhooks in the app.