{
 "categories": [
  "government",
  "public-sector",
  "data-exchange"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-09-03",
   "fact": "homepage",
   "note": "KS Digital presents Fiks protokoll as the Fiks-platform integration service that standardises asynchronous, end-to-end-encrypted exchange between municipal systems, with municipal control in Fiks-konfigurasjon.",
   "source": "https://ksdigital.no/tjenestene/fiks-protokoll/",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "vendor",
   "note": "KS Fiks developer docs list support at fiks@ksdigital.no and describe Fiks Protokoll as a Fiks-platform service configured in Fiks Forvaltning.",
   "source": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "license",
   "note": "Use requires a hovedavtale. Fiks protokoller are Digifin-financed with a one-time Digifin charge. KS invoices for protocol use, and suppliers may add their own costs.",
   "source": "https://ksdigital.no/tjenestene/fiks-protokoll/",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.api.exists",
   "note": "KS Digital documents machine-to-machine APIs only. The interface table lists web portal as Nei and maskin-til-maskin as API. Fiks Protokoll and Fiks IO Katalog APIs create and look up protocol accounts after a system is created.",
   "source": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.api.kinds[0]",
   "note": "Other accounts send to a Fiks IO account through the Fiks IO REST API by specifying MottakerKontoId. The page shows the JSON send body, including MeldingType such as no.ks.fiks.arkiv.v1.arkivering.arkivmelding.",
   "source": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/fiksio/index.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.api.kinds[1]",
   "note": "Fiks IO uses RabbitMQ/AMQP queues. The organisation receives messages by establishing an AMQP connection to io.fiks.ks.no. Delivery is push rather than pull.",
   "source": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/fiksio/index.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.api.kinds[2]",
   "note": "Opened the published OpenAPI 3.0.1 spec titled KS Fiks: Protokoll, including Protokoll-konfigurasjon endpoints such as POST /fiks-protokoll/api/v1/konfigurasjon/{fiksOrgId}/systemer/{systemId}/kontoer.",
   "source": "https://developers.fiks.ks.no/api/fiks-protokoll-konfigurasjon-api-v1.json",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.api.auth[0]",
   "note": "Server-to-server Fiks integrations fetch an OAuth 2.0 JWT from Maskinporten with scope ks:fiks, signed with a virksomhetssertifikat. Self-signed certificates are not accepted.",
   "source": "https://developers.fiks.ks.no/felles/integrasjoner/",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.api.auth[1]",
   "note": "Every integration call also requires IntegrasjonId and IntegrasjonPassord headers from Fiks-konfigurasjon, in addition to the Maskinporten bearer token.",
   "source": "https://developers.fiks.ks.no/felles/integrasjoner/",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.api.coverage",
   "note": "Coverage is versioned protocol messaging plus account and catalogue administration. It is not a general municipal application API and is not designed or sized for bulk migration. Fiks IO docs state it does not replace SvarUt/SvarInn.",
   "source": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.api.docs",
   "note": "Opened as the current Fiks Protokoll service page, including protocol list, account model, OpenAPI pointers, and the Fiks IO transport link.",
   "source": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.sdk.exists",
   "note": "KS lists official Fiks IO send and send-plus-receive clients for Java and .NET under Fiks IO og Fiks Protokoll, distributed on Maven Central and nuget.org.",
   "source": "https://developers.fiks.ks.no/felles/klientbiblioteker/index.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.sdk.languages[0]",
   "note": "KS documents fiks-io-klient-java and fiks-io-send-klient as official Java clients for receive-and-send and send-only.",
   "source": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/fiksio/index.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.sdk.languages[1]",
   "note": "KS documents KS.Fiks.IO.Client and KS.Fiks.IO.Send.Client as official .NET clients for receive-and-send and send-only.",
   "source": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/fiksio/index.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.sdk.official",
   "note": "The klientbiblioteker page presents these Java and .NET packages as the official KS client libraries for Fiks IO and Fiks Protokoll.",
   "source": "https://developers.fiks.ks.no/felles/klientbiblioteker/index.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.extensibility.scripting[0]",
   "note": "A Fiks integration is a machine client created in Fiks forvaltning and authorised per organisation and per service. Each Protokoll system gets an integration used for all accounts under that system.",
   "source": "https://developers.fiks.ks.no/felles/integrasjoner/",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.extensibility.scripting[1]",
   "note": "KS publishes OpenAPI specifications for generating clients and model objects, for example with Swagger Codegen.",
   "source": "https://developers.fiks.ks.no/felles/integrasjoner/",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.data_access.export[0]",
   "note": "Opened the Fiks IO Katalog OpenAPI 3.0.1 spec. GET /fiks-io/katalog/api/v1/kontoer/{kontoId}/status returns gyldigAvsender, gyldigMottaker, antallKonsumenter, and antallUavhentedeMeldinger.",
   "source": "https://developers.fiks.ks.no/api/fiksio-katalog-api-v1.json",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.data_access.export[1]",
   "note": "GET /fiks-io/katalog/api/v1/kontoer/{kontoId}/offentligNokkel returns the account public key used to encrypt messages to that account.",
   "source": "https://developers.fiks.ks.no/api/fiksio-katalog-api-v1.json",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.data_access.export[2]",
   "note": "Receive maps AMQP headers into MottattMeldingMetadata. Protocol message types such as no.ks.fiks.arkiv.v1.arkivering.arkivmelding carry the structured payload.",
   "source": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/fiksio/index.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.data_access.import[0]",
   "note": "KS clients and KS-specified protocols use signed and encrypted ASiC-E containers. Files larger than 5 MB go through Fiks Dokumentlager, up to 5 GB.",
   "source": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/fiksio/index.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.data_access.import[1]",
   "note": "After a protocol system exists, suppliers create accounts, upload a public key, set protocol parties, and grant access through the configuration API.",
   "source": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/konfigurasjon-api/index.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "https://developers.fiks.ks.no/llms.txt returned HTTP 404 on 2026-09-03. https://ksdigital.no/llms.txt also returned 404.",
   "source": "https://developers.fiks.ks.no/llms.txt",
   "tier": "scraped"
  },
  {
   "date": "2026-09-03",
   "fact": "verdict.scores.api",
   "note": "Documented REST send, AMQP receive, OpenAPI, and official Java/.NET clients are a usable production path. The score stays at useful-with-material-limits because live use needs a hovedavtale, Digifin terms, Maskinporten with virksomhetssertifikat, IntegrasjonId/passord, and per-system grants; Fiks IO has no delivery guarantee; and the service is not for bulk migration.",
   "source": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/fiksio/index.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as the current Fiks Protokoll service page, including protocol names, account model, and OpenAPI pointers.",
   "source": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the current Fiks IO transport page, including REST send, AMQP receive, Maskinporten, and the explicit non-replacement of SvarUt/SvarInn.",
   "source": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/fiksio/index.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as the current Fiks integration and Maskinporten authentication guide.",
   "source": "https://developers.fiks.ks.no/felles/integrasjoner/",
   "tier": "declared"
  },
  {
   "date": "2026-09-03",
   "fact": "freshness.watch[3].url",
   "note": "Opened and verified as the current OpenAPI 3.0.1 Fiks Protokoll configuration spec.",
   "source": "https://developers.fiks.ks.no/api/fiks-protokoll-konfigurasjon-api-v1.json",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-09-03",
  "volatility": "medium",
  "watch": [
   {
    "type": "docs",
    "url": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/"
   },
   {
    "type": "docs",
    "url": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/fiksio/index.html"
   },
   {
    "type": "docs",
    "url": "https://developers.fiks.ks.no/felles/integrasjoner/"
   },
   {
    "type": "docs",
    "url": "https://developers.fiks.ks.no/api/fiks-protokoll-konfigurasjon-api-v1.json"
   }
  ]
 },
 "homepage": "https://ksdigital.no/tjenestene/fiks-protokoll/",
 "id": "ks-fiks-protokoll",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": false
  },
  "api": {
   "auth": [
    "maskinporten",
    "integrasjon-id-password"
   ],
   "coverage": "partial",
   "docs": "https://developers.fiks.ks.no/tjenester/fiksprotokoll/",
   "exists": true,
   "kinds": [
    "rest",
    "amqp",
    "openapi"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "konto-status",
    "offentlig-nokkel",
    "protocol-messages"
   ],
   "import": [
    "asic-e-message",
    "public-key"
   ]
  },
  "extensibility": {
   "scripting": [
    "fiks-integrasjon",
    "openapi-codegen"
   ],
   "webhooks": "unknown"
  },
  "integrations": {
   "make": "unknown",
   "n8n": "unknown",
   "power_automate": "unknown",
   "zapier": "unknown"
  },
  "mcp": {
   "first_party": "unknown",
   "third_party": [],
   "verdict": "unknown"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. Fiks Protokoll documents no web portal for message exchange. The machine path is Fiks IO REST send plus AMQP receive, and the Fiks Protokoll and Fiks IO Katalog REST APIs. Portal UI automation is not the supported path.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": true,
   "languages": [
    "java",
    "csharp"
   ],
   "official": true
  }
 },
 "name": "KS Fiks Protokoll",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "ks-fiks-svarut",
   "ks-fiks-digisos",
   "eformidling"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "KS Digital",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 6,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": null,
   "overall": 6,
   "rpa": null
  },
  "summary": "KS Fiks Protokoll is automatable as KS Digital's versioned municipal machine-to-machine protocol bus, with Fiks IO as the transport, not as KS Fiks SvarUt, KS Fiks Digisos, or Digdir eFormidling. Protocols documented on the opened pages include Arkiv, Plan, Matrikkelf\u00f8ring, Barnevern (KOSTRA), Link, and Saksfaser. A protokollkonto is a wrapper on a Fiks IO account and cannot talk to a raw Fiks IO account. Send is REST; receive is AMQP/RabbitMQ at io.fiks.ks.no. Authentication is the Fiks integration model: a Maskinporten OAuth 2.0 JWT with scope ks:fiks, signed with a virksomhetssertifikat, plus IntegrasjonId and IntegrasjonPassord headers. KS publishes OpenAPI 3.0.1 specs for protocol configuration and the Fiks IO catalogue, and official Java and .NET Fiks IO clients. Fiks IO explicitly does not replace SvarUt/SvarInn and does not guarantee delivery. The service is for daily structured exchange, not bulk migration. Live use needs a KS Digital hovedavtale, Digifin terms, a virksomhetssertifikat, Maskinporten, and per-system grants. That agreement and Maskinporten gate is the material limit. First-party MCP ownership is not established. Computer-use viability is unassessed.\n"
 }
}