{
 "categories": [
  "government",
  "public-sector"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-09-04",
   "fact": "homepage",
   "note": "KS Fiks developer docs present Fiks Innsyn as the metadata search engine for municipal post, cases, invoices, forms, and properties, used by min.kommune.no and by municipal minside integrations.",
   "source": "https://developers.fiks.ks.no/tjenester/minkommune/innsyn/",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "vendor",
   "note": "KS Digital's Min kommune product page states that inhabitant information is fetched from an encrypted Fiks Innsyn database fed by municipal integrations. KS Digital is the steward.",
   "source": "https://ksdigital.no/tjenestene/minkommune/",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "license",
   "note": "Taking Min kommune / Innsyn into use requires a signed KS Digital hovedavtale. KS Digital states there is no extra service price for Min kommune itself, but the service sits on the commercial Fiks contract.",
   "source": "https://ksdigital.no/tjenestene/minkommune/",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "modalities.api.exists",
   "note": "The opened page documents Index API version 2, a delete API, named search APIs, and Innsyn Oppslag as REST interfaces for integrators.",
   "source": "https://developers.fiks.ks.no/tjenester/minkommune/innsyn/",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "modalities.api.kinds[0]",
   "note": "Opened OpenAPI 3.0.1 for KS Fiks: Innsyn Index Service v2. PUT /innsyn-index/api/v2/indexRequest accepts a JSON batch on https://api.fiks.ks.no and https://api.fiks.test.ks.no/.",
   "source": "https://developers.fiks.ks.no/api/innsyn-index-api-v2.json",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "modalities.api.kinds[1]",
   "note": "Each Index, delete, search, and Oppslag operation is linked to an OpenAPI document hosted under developers.fiks.ks.no/api/.",
   "source": "https://developers.fiks.ks.no/tjenester/minkommune/innsyn/",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "modalities.api.auth[0]",
   "note": "Server-to-server Fiks integrations, including upload of messages to Fiks Innsyn, fetch an OAuth 2.0 JWT from Maskinporten with scope ks:fiks, signed with a virksomhetssertifikat.",
   "source": "https://developers.fiks.ks.no/felles/integrasjoner/",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "modalities.api.auth[1]",
   "note": "Every integration call also requires IntegrasjonId and IntegrasjonPassord headers from Fiks-konfigurasjon, in addition to the bearer token. The page's search example posts to /innsyn-sok/api/v1/sok with those headers.",
   "source": "https://developers.fiks.ks.no/felles/integrasjoner/",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "modalities.api.auth[2]",
   "note": "Search and Oppslag must use integrasjon-person authentication: the logged-in inhabitant's ID-porten token plus IntegrasjonId and IntegrasjonPassord, and the innsyn s\u00f8k privilege on the Fiks organisation.",
   "source": "https://developers.fiks.ks.no/tjenester/minkommune/innsyn/",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "modalities.api.coverage",
   "note": "Coverage is metadata index, search, and lookup. The engine does not store document bytes. Exposure is by f\u00f8dselsnummer, organisasjonsnummer, matrikkelnummer, or offentlig. Index v1 is legacy. Results are filtered by ID-porten security level and the signed-in person.",
   "source": "https://developers.fiks.ks.no/tjenester/minkommune/innsyn/",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "modalities.api.docs",
   "note": "Opened as the current Fiks Innsyn developer page covering components, index rules, message types, search APIs, Oppslag, and auth.",
   "source": "https://developers.fiks.ks.no/tjenester/minkommune/innsyn/",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "modalities.extensibility.scripting[0]",
   "note": "A Fiks integration is a machine client created in Fiks forvaltning and authorised per organisation. The page uses Fiks Innsyn index upload as the example server-to-server task.",
   "source": "https://developers.fiks.ks.no/felles/integrasjoner/",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "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-04",
   "fact": "modalities.extensibility.scripting[2]",
   "note": "ks-no/fiks-innsyn-json-schema publishes JSON Schema for Innsyn index metadata and a Maven artifact no.ks.fiks:innsyn-json-schema with generated Java POJOs. That is schema codegen, not a separately versioned HTTP client.",
   "source": "https://raw.githubusercontent.com/ks-no/fiks-innsyn-json-schema/main/README.md",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "modalities.data_access.export[0]",
   "note": "Opened Multi-s\u00f8k OpenAPI. POST /innsyn-sok/api/v1/multi/sok searches all message types; additional POSTs cover aggregation and last-login search.",
   "source": "https://developers.fiks.ks.no/api/openapi-sok-multi-v1.json",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "modalities.data_access.export[1]",
   "note": "Opened Oppslag OpenAPI. GET /innsyn-sok/api/v1/oppslag/dokument, /oppslag/korrelasjon, and /oppslag/forelder retrieve one message, a correlation group, or children of a parent.",
   "source": "https://developers.fiks.ks.no/api/openapi-oppslag-v1.json",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "modalities.data_access.import[0]",
   "note": "PUT /innsyn-index/api/v2/indexRequest indexes or updates a batch. 422 is documented when the batch exceeds 5000 messages. Delete is a separate OpenAPI at innsyn-delete-api-v1.json.",
   "source": "https://developers.fiks.ks.no/api/innsyn-index-api-v2.json",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "https://developers.fiks.ks.no/llms.txt returned HTTP 404 on 2026-09-04.",
   "source": "https://developers.fiks.ks.no/llms.txt",
   "tier": "scraped"
  },
  {
   "date": "2026-09-04",
   "fact": "verdict.scores.api",
   "note": "Documented REST index, search, and Oppslag with OpenAPI is a usable production path. The score stays in the useful-with-limits tier because live use needs a KS Digital hovedavtale, Maskinporten or ID-porten, IntegrasjonId/passord, Innsyn privileges, and the API is metadata-only.",
   "source": "https://developers.fiks.ks.no/tjenester/minkommune/innsyn/",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as the current Fiks Innsyn developer page.",
   "source": "https://developers.fiks.ks.no/tjenester/minkommune/innsyn/",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the current Fiks integration and Maskinporten / ID-porten authentication guide.",
   "source": "https://developers.fiks.ks.no/felles/integrasjoner/",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as the current Index API v2 OpenAPI document.",
   "source": "https://developers.fiks.ks.no/api/innsyn-index-api-v2.json",
   "tier": "declared"
  },
  {
   "date": "2026-09-04",
   "fact": "freshness.watch[3].url",
   "note": "Opened and verified as the current KS Digital how-to for creating an Innsyn integration with Innsyn-indeksering and Innsyn-s\u00f8k privileges.",
   "source": "https://ksdigital.no/tjenestene/minkommune/ta-i-bruk-innsyn-via-fagsystem-minkommune/",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-09-04",
  "volatility": "medium",
  "watch": [
   {
    "type": "docs",
    "url": "https://developers.fiks.ks.no/tjenester/minkommune/innsyn/"
   },
   {
    "type": "docs",
    "url": "https://developers.fiks.ks.no/felles/integrasjoner/"
   },
   {
    "type": "docs",
    "url": "https://developers.fiks.ks.no/api/innsyn-index-api-v2.json"
   },
   {
    "type": "docs",
    "url": "https://ksdigital.no/tjenestene/minkommune/ta-i-bruk-innsyn-via-fagsystem-minkommune/"
   }
  ]
 },
 "homepage": "https://developers.fiks.ks.no/tjenester/minkommune/innsyn/",
 "id": "ks-fiks-innsyn",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": false
  },
  "api": {
   "auth": [
    "maskinporten",
    "integrasjon-id-password",
    "id-porten"
   ],
   "coverage": "partial",
   "docs": "https://developers.fiks.ks.no/tjenester/minkommune/innsyn/",
   "exists": true,
   "kinds": [
    "rest",
    "openapi"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "search-results",
    "oppslag-melding"
   ],
   "import": [
    "index-metadata-batch"
   ]
  },
  "extensibility": {
   "scripting": [
    "fiks-integrasjon",
    "openapi-codegen",
    "json-schema-models"
   ],
   "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. min.kommune.no SPAs search the Innsyn index after ID-porten login. The documented machine path is Index API v2 plus the search and Oppslag REST APIs, not browser control of min.kommune.no. This record is Fiks Innsyn, not Min kommune as a second product.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "KS Fiks Innsyn",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "ks-fiks-svarut",
   "ks-fiks-digisos",
   "ks-fiks-protokoll",
   "einnsyn"
  ],
  "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 Innsyn is automatable as KS Digital's municipal citizen-metadata index and search service, not as KS Fiks SvarUt, Digisos, Protokoll, or Digdir eInnsyn, and not as min.kommune.no as a second product. Integrators PUT batches of up to 5000 messages to Index API v2 at /innsyn-index/api/v2/indexRequest with Base64 JSON metadata (FAKTURA_V1, INNSENDT_SKJEMA_V1, SKJEMAKLADD_V1, MAPPE_V1, JOURNALPOST_V1). Indexing is a cache: messages can be deleted by a service administrator, so producers must support replay. Search APIs cover Eiendom, Faktura, Post, Skjema, Multi, and a legacy endpoint; Oppslag retrieves one message, a correlation group, or children of a parent. The index stores metadata and links, not document bytes. Server-to-server index calls use a Maskinporten OAuth 2.0 JWT with scope ks:fiks plus IntegrasjonId and IntegrasjonPassord. Search and Oppslag use integrasjon-person: the inhabitant's ID-porten token with the same integration headers and the innsyn s\u00f8k privilege. Live use needs a KS Digital hovedavtale, a virksomhetssertifikat, Maskinporten or ID-porten client setup, and per-organisation privileges. Vendor documentation does not settle first-party MCP ownership. Computer-use viability is unassessed.\n"
 }
}