Skip to content

For Accountants

An API with documented scope

Automate workspace resources with an API key and query consolidated aging for authorised workspaces through the accountant-specific endpoint.

The public API exposes the resources in its OpenAPI contract. Today, the verified accountant-specific multi-client operation is consolidated aging; we do not present undocumented portfolio, batch-tax or document-request endpoints as live.

What you can do

Consolidated multi-client aging

POST /v1/gestoria/aging accepts up to 200 workspaces and returns data only for those where the caller has authorised membership.

Invoices and clients per workspace

Read or create documented resources with a workspace API key. A universal token is not shared across clients.

OpenAPI 3.1 contract

Check methods, payloads and responses at /openapi.yaml before integrating; the published contract takes precedence over marketing examples.

Documented webhooks

Create subscriptions through /v1/webhooks and use published events with HMAC-SHA256 signatures and retries.

Remote MCP

The remote MCP server exposes 157 tools and uses OAuth 2.0 + PKCE. It is separate from the X-API-Key REST API.

Requests and messaging

Document-request and contextual-messaging flows remain in beta and are not advertised as public REST endpoints.

Authentication and authorisation

The REST API uses X-API-Key and applies workspace scope. POST /v1/gestoria/aging re-checks the accountant’s membership for every requested workspace. Remote MCP uses OAuth 2.0 + PKCE; the two mechanisms are not interchangeable.

Most used endpoints

Method Path Purpose
POST /v1/gestoria/aging Consolidated aging for authorised workspaces.
GET /v1/invoices List invoices in the authenticated workspace.
POST /v1/invoices Create an invoice in the authenticated workspace.
GET /v1/clients List clients in the authenticated workspace.
GET /v1/webhooks List webhook subscriptions for the workspace.
GET /openapi.yaml Read the current OpenAPI 3.1 contract.

Full documentation is at docs.frihet.io. Volume, support or a dedicated SLA require an explicit agreement; this page does not guarantee them.

See API documentation

If you automate with n8n or your own scripts, we review the published contract and pilot scope with you.