Skip to content
On this page

Changelog & roadmap

2026-09

  • Strict input. Every query parameter and body field outside an endpoint's documented contract is now a 422 naming the key — unknown, read-only or renamed — instead of being silently dropped. One date vocabulary on every list and report: date_from/date_to (start_date/end_date and from/to are refused with the replacement named); per_page is bounded to 100; every paginated list is tie-broken by id. /payments gained customer_id, date_from/date_to, search and sort; payment status, currency, amount and invoice_id are server-owned. MCP tools refuse unknown arguments the same way. See Errors and Pagination.
  • One error envelope. Every /api/v1 error is JSON — even without Accept: application/json — with success, error, message and errors; errors is always an object. Previously a validation error sent without that header was redirected to an HTML page. See Errors.
  • Business-rule refusals are 422. Refusals such as paying more than the balance due or billing a non-billable expense now return 422 with the field named in errors, instead of 500.
  • Ids in request bodies are checked against your organization. A customer_id, contact_id, invoice_id or user_id from another organization is rejected with 422, exactly like one that does not exist.

2026-07

  • New documentation pipeline. The OpenAPI specification, this documentation, and the Bruno collection are now generated from the codebase on every change, so they cannot drift from the live API.
  • Banking (read-only). GET /api/v1/bank-accounts, GET /api/v1/bank-transactions and statement import (POST /api/v1/bank-accounts/{id}/import-statement, CAMT.053 / CODA) are available.

2026-06

  • Receipt OCR. Asynchronous receipt upload (POST /api/v1/expenses/upload-receipt) with polling (GET /api/v1/expenses/ocr/{receipt_ref}).
  • OAuth 2.0 + PKCE is the supported sign-in flow for user-facing apps; the password grant is deprecated and will be removed.

Roadmap

Planned — not yet available, details may change:

  • Bank reconciliation: matching bank transactions to invoices and expenses, with reconciliation endpoints.
  • Compound & inclusive tax handling across invoices and expenses.
  • Region-coded subdivisions (ISO 3166-2) on customer and organization addresses.

Endpoints only appear in the specification and reference once they actually exist — anything listed here is subject to change until released.