Skip to content

Build on Konto

Konto exposes your accounting — customers, invoices, expenses, tasks and product sales — through an HTTP API and an MCP connector. This portal covers both, and helps you pick the one that fits.

Which path fits you?

  • :material-robot-happy: MCP connector — no code

    Connect Konto to Claude, ChatGPT, Cursor or any MCP client and run your books in plain language. Best for AI assistants and quick automations.

    :octicons-arrow-right-24: Connect an AI assistant

  • :material-account-key: Agent API (OAuth2) — act for a user

    Build an app that a Konto user signs into and grants scoped access — the same surface the MCP uses. Best for user-facing products (a Shopify app, a portal).

    :octicons-arrow-right-24: Quickstart · Reference

  • :material-server-network: Legacy REST (api_key) — server-to-server

    A service that runs on its own (a billing cron, an ERP sync) authenticates with a username + api_key. Best for headless back-office integrations.

    :octicons-arrow-right-24: In-app reference

Not sure? Start here

  • A person will use it inside an AI tool → MCP connector.
  • Your app acts on behalf of a signed-in Konto user → Agent API.
  • Your service runs unattended (no user to log in) → Legacy REST.

Two environments

Host Sign in with Use for
Production https://konto.is a real Konto account live customers — real invoices & email
Development https://dev.konto.is a dev/test account building and testing, safely

Always build against development first. See Environments & sandbox.

Writes are real

Creating an invoice issues it and Konto delivers it to the customer. On production that means a real invoice to a real person. Read The write contract before you create anything.

What you can do

Customers · Items (products/services) · Invoices & credit notes · Recurring invoices · Costs/expenses (incl. receipt OCR) · Tasks & time tracking · Product sales — each gated by a scope the user grants at sign-in (details).

Next steps

  1. Quickstart — your first call in five minutes.
  2. Authentication & scopes — the OAuth flow.
  3. The write contract — the rules that make writes succeed.
  4. Recipes — CRM sync, ERP plugin, time-billing, subscriptions.