REST API. Every action, every feature.

160 endpoints across 14 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 · 14

Invoices15 routes

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

Expenses21 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.

Bank Accounts5 routes

Banking details for invoice payment instructions.

Organizations10 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.

Integrations16 routes

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

Settings3 routes

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

Companion11 routes