Skip to content

Recipes

Common integrations, with the scopes and endpoints each needs. All examples use the Agent API; the write contract covers the field rules.

CRM → Konto customer sync

Keep customers in sync from a CRM (HubSpot, Pipedrive, …).

  • Scope: manage_customers
  • Endpoints: GET /agent/customers?kennitala=… · POST /agent/customers · GET /agent/customers/{guid} · PUT /agent/customers/{guid}

Pattern: on a CRM change, look the contact up by kennitala first (?kennitala=). If found, PUT the changes to its guid; if not, POST a new one. Remember create doesn't dedupe — always look up before creating.

ERP / Business Central plugin

Push posted sales as Konto invoices, and pull Konto costs into the ledger.

  • Scopes: create_invoice, nav, cost
  • Endpoints: POST /agent/invoices · PUT /agent/invoices/{guid} (accounting status) · GET /agent/costs?from_date=… · PUT /agent/costs/{guid}

Pattern: map each ERP sales document to an invoice payload (respect the amount = Σ + VAT rule and the date chain), POST it, and store the returned guid against your ERP record. Sync accounting status back with the PUT status endpoints. This is often better as a server-to-server integration on the legacy api_key API — no user to keep signed in.

Project tool → time-billing

Turn tracked time into invoices (from Jira, Asana, a PM tool…).

  • Scopes: task, create_invoice
  • Endpoints: POST /agent/tasks · POST /agent/tasks/{guid}/end (with adv:1, date, h, p to log dated hours) · GET /agent/tasks?type=invoice · POST /agent/invoices

Pattern: create a task per project/customer, log time as dated entries, then list type=invoice (tasks ready to bill) and raise invoices from the accumulated hours (uom: HUR).

Subscription / recurring billing

Bill a plan on a schedule — SaaS seats, a bread-delivery round, memberships.

  • Scope: recurring (+ manage_customers to onboard)
  • Endpoints: POST /agent/customers · POST /agent/recurring-invoices

Pattern: onboard the customer, then create one recurring-invoice template with recurring_interval (weekly/monthly/quarterly/yearly), recurring_start_date, optional recurring_max_invoice, and the line items — Konto generates the invoices automatically. Don't loop POST /agent/invoices on a cron; that's what recurring invoices are for.

Need something not covered here? The full surface is in the API reference.