API changelog

Policy

The Apier.no API is additive by contract: existing response fields never change semantics or type, and fields are never removed, without a /v2 version bump. New fields may be added to any response at any time — agents should ignore unknown fields.

The Rulebook has its own version (_meta.rulebook_version on every response). A Rulebook bump can change which obligations apply to a given company but cannot change the response shape.

Entries

A curated, newest-first list of user-visible changes to the API, the MCP tools, and capability statuses. Dates are the day each change shipped or the day a capability status changed. Where a change affects which obligations apply to a company, the _meta.rulebook_version on the response moves with it.

For the current state of every capability — what is live, what is in beta, and what is waiting on Norwegian government access — see the roadmap and the capability status page.

2026-06-15 — Account-change webhooks (beta)

Subscribe to signed accounts.updated notifications and get a callback when a monitored company's annual-accounts status changes. Deliveries are HMAC-signed; subscriptions are managed through the API. Beta — register and test before depending on it in production.

2026-06-15 — Signed verification certificates

Company verification and signing-authority responses can now return a signed (JWS) certificate. Archive it and re-verify the verdict later without re-querying — useful for audit files and onboarding records.

2026-06-11 — Signing-authority endpoint

Resolve who may legally sign for a Norwegian company. The response gives a structured verdict plus the rule basis behind it, so an agent can explain why a person can or cannot act.

2026-06-10 — Annual-accounts status endpoint

Check whether a company has filed its annual accounts, returned as a normalised status field rather than a raw registry dump.

2026-06-09 — Company verification verdict

A single endpoint that returns a structured verification verdict for a company from registry data — a building block for know-your-business (KYB) and onboarding checks.

2026-06-09 — Altinn 3 System Register accreditation confirmed

Apier is registered as an Altinn 3 system vendor and the required Altinn access packages were granted — a prerequisite for live government submissions on a customer's behalf.

2026-06-06 — Maskinporten production access verified

The production Maskinporten client was verified, enabling live machine-to-machine authentication against Norwegian government infrastructure.

2026-06-05 — 13 MCP tools and per-client setup

The full Model Context Protocol tool set went live — company lookup, obligations, deadlines, verification, signing authority, and more — with setup guides for Claude Desktop, Cursor, and other MCP clients.

2026-05-30 — MCP server published

The Apier MCP server (@apier-no/mcp) was published to npm and listed in the public MCP directory, so agents can discover and add it directly.

2026-05-29 — VAT-return submission access granted

Skatteetaten granted access for MVA-melding (VAT-return) validation and submission, in both test and production. Live binding submission is in beta validation; validation and dry-run are available today.

2026-05-10 — Self-serve signup and instant API key

Sign up, confirm with a magic link, and receive a free-tier API key to make your first authenticated call — no sales call, no waiting.

2026-04-23 — Documentation site and Quick Start

The documentation site and the Quick Start guide went live, covering authentication and a first end-to-end request.

2026-04-16 — OpenAPI 3.1 specification

The API contract was published as a single OpenAPI 3.1 source of truth, linted in continuous integration on every change so the published spec never drifts from the live API.