REST API. Every action, every feature.

239 endpoints across 20 features. Authenticate with a Bearer API key, scope it to the features you need, and call the same routes the dashboard calls. The OpenAPI 3.1 spec is at /api/openapi.json.

Features · 20

Invoices19 routes

Document creation, sending, and payment tracking. Covers invoices, receipts, payment requests, credit/debit memos, and clearance flows for jurisdictions that require it.

Payments2 routes

Settlement recording and allocation across document lines, including partial and multi-document payments.

Expenses25 routes

Expense logging, OCR scanning, email ingestion, vendor matching, and approval workflow.

Customers9 routes

Customer records (external and in-system suppliers' clients), recipients for invoice delivery.

Suppliers9 routes

Supplier directory, cross-org invitations, accepted supplier catalogs.

Orders9 routes

Purchase orders from clients to suppliers, including the supplier-side reverse view.

Logistics8 routes

Item catalog, stock levels, and stock-movement audit trail.

Reports3 routes

Pre-built and country-specific financial reports — income, expenses, AR aging, tax compliance.

Accounting7 routes

General-ledger overlay — authored journal entries (opening balances, adjustments) and accounting periods with close/lock. Statements (trial balance, balance sheet) are served as reports.

Payroll14 routes

Payroll runs — month payslip generation/approval, salary advances, and net/statutory settlement. Compensation-bearing; employment records themselves are `hr`.

Hr24 routes

Human resources — the employee roster and its employment records (a Counterparty extension), employment terms, leave and employee master data. Carries employee PII; excludes compensation, which is `payroll`.

Attendance8 routes

Time and attendance — work sessions, punches and timesheets. Split from `hr` so a time-clock or scheduling integration can be granted punches without every employee's PII.

Bank Accounts5 routes

Banking details for invoice payment instructions.

Organizations12 routes

Tenant management — create, configure, manage org-level settings and tax-authority integrations.

Users28 routes

Org membership, role management, invitations, and notifications.

Automations13 routes

Scheduled and triggered workflows — wire any platform event to any API action. An automation is a graph of TRIGGER/FILTER/ACTION blocks joined by edges: discover the block catalog (GET /api/automations/actions), create the graph in DRAFT, test it synchronously, then enable it to arm.

Integrations22 routes

Email inbox connections (Gmail/Outlook/IMAP/POP3) and tax-authority credential management.

Imports8 routes

Settings3 routes

Caller's own preferences and platform utilities (e.g. exchange-rate refresh).

Companion11 routes

AI companion sessions — conversations, turns, streamed output and run logs. A turn is an automation run under the caller's own principal, so it can reach only what the caller can.