Postman¶
Two collections are available.
Agent API (OAuth2) — generated from the spec¶
Generated directly from openapi.yaml, so it stays in sync with
the reference. Requests are foldered by resource (Customers, Invoices, Costs, …).
:material-download: Download the Agent API collection
Import it: in Postman → Import → drop the downloaded file (Postman v2.1 format), or paste the raw URL.
Set these collection variables after importing:
| Variable | Development | Production |
|---|---|---|
baseUrl |
https://dev.konto.is |
https://konto.is |
bearerToken |
your dev access token | your prod access token |
- Get a
bearerTokenby completing the OAuth flow (or copy theaccess_tokenfrom the Quickstart). - On development, also add
en4_maint_codeas a query param on each request (dev runs in maintenance mode) — ask Konto for the code.
Auth
Every resource request uses Authorization: Bearer {{bearerToken}}. Set the
token once at the collection level and all requests inherit it.
Legacy REST (api_key) — hand-maintained¶
For the server-to-server surface (username + api_key), use Konto's existing
published collection:
:material-open-in-new: Open the Konto API collection on Postman
Prefer not to use Postman? The same requests are copy-pasteable as curl in the
Quickstart, and the full endpoint list is in
the API reference.