Skip to content
Apier.no

API changelog

Notable changes to the Apier.no API and docs.

[Cite this as: Apier.no Docs v0.1.0 — last updated 2026-11-19]

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-11-19 — Price tiers from 2026-12-07: Verify, Authority and Proof

From 2026-12-07 at 00:00 Europe/Oslo a metered call is charged by price tier instead of the flat 50 øre per call. Verify (company facts: status, legal form, VAT registration, bankruptcy and liquidation flags, registered roles, obligations, deadlines and annual accounts) costs 10 øre, USD 0.01. Authority (reads that return the register's coded signing rules for the company) costs 60 øre, USD 0.06. Proof (a signed evidence pack) costs 300 øre, USD 0.30. Point-in-time and history reads are charged the Verify price. Both prices are fixed and neither is converted from the other at an exchange rate; the prepaid wallet is debited in NOK. Until that date every metered call still costs 50 øre. A bulk verification job keeps the per-item price in force when it was created: a job created before that instant is charged 50 øre per answered company, also for items answered after it, and a job created from that instant is charged the Verify price. Free keyless endpoints and tools stay free, and existing wallet balances are unchanged. GET /api/v1/pricing, /pricing.json and the get_pricing tool now return the tiers, the tier of every billable endpoint and metered MCP tool, the free surfaces and effective_from; cost_ore there is the price charged at the time of the answer.

2026-10-21 — Altinn Autorisasjon, fullmakt and acting-capacity surfaces withdrawn

Altinn Servicedesk answered in writing on 2026-10-21, after legal review, that Altinn Autorisasjon data may not be the basis of a commercial service, with or without a systembruker. Apier has therefore withdrawn every surface that read, brokered or served Altinn rights, access packages, delegations or fullmakt state: the /api/v1/fullmakt/* routes, acting capacity, delegation status, the Altinn filing history, the filing action routes, and the MCP tools request_fullmakt, check_fullmakt, revoke_fullmakt, list_acting_capacity, check_authorization, validate_action and get_company_filing_history. The routes stay published and answer HTTP 410 with the new error code CAPABILITY_WITHDRAWN; the tools left tools/list. Brønnøysund's signaturrett and prokura data is unaffected: GET /api/v1/company/{org}/authority remains the place to read who may sign for a company.

The MVA submission line is parked from the same date (see the 2026-05-29 entry). What remains of it on MCP is submit_vat_return: a sandbox-only VAT return rehearsal (scope read:actions) that previews without an approval token or files a mock receipt with one, and never contacts a government system. It is not listed in tools/list and stays callable by name. Since 2026-11-18 the MCP reference records this tool and the withdrawn tools here instead of in its tool tables.

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

Read the register's signing rule for a Norwegian company. When the register's coded data is available, the response gives the coded signing combinations, their classification and the rule basis behind them, so an agent can show which registered combination applies to its own action; when it is not, the classification falls back to the registered role holders.

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 registration not yet confirmed (corrected — originally titled "Altinn 3 System Register accreditation confirmed")

Correction (2026-10-21): the Altinn 3 System Register registration no longer matters for this API. Altinn Servicedesk answered in writing on 2026-10-21 that Altinn Autorisasjon data may not be the basis of a commercial service, so every Altinn access-package, system-user and fullmakt surface is withdrawn (HTTP 410 CAPABILITY_WITHDRAWN); see the 2026-10-21 entry above. The earlier correction follows for the record. Correction (2026-10-15): this entry overstated what was in place. Apier's own approvals record shows the Altinn 3 System Register registration as submitted and awaiting confirmation, with no confirmation recorded on this date or since, and no Altinn access package is recorded as granted. Access packages are not granted to a system vendor at all: each customer delegates them to the vendor's system user in its own Altinn portal. Binding submission on a customer's behalf is not available. See the capability status page for the current operational state. The original (incorrect) text is preserved below for the record.

Archived — original entry text (incorrect): 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 test-client verification (corrected — originally titled "production access verified")

Correction (2026-08-12): this entry overstated what was verified. What was actually verified is the Maskinporten test client's credentials and the client-assertion signing path — no production Maskinporten client is registered, and no live machine-to-machine authentication against Norwegian government infrastructure is enabled (MASKINPORTEN_MODE runs as mock in production). See the capability status page for the current operational state. The original (incorrect) text is preserved below for the record.

Archived — original entry text (incorrect): 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 validation access granted (corrected — originally titled "VAT-return submission access granted")

Correction (2026-10-21): validation and dry-run are no longer available either. The dry-run read Altinn delegation state, and the MVA submission line is parked and not offered, so POST /api/v1/actions/execute answers HTTP 410 CAPABILITY_WITHDRAWN in both modes; see the 2026-10-21 entry above. The earlier correction follows for the record. Correction (2026-10-01): this entry overstated what was granted. On 2026-05-29 Skatteetaten approved Apier for the MVA-melding (VAT-return) validation API, in test and production. That approval did not cover submission. Binding submission in production is not yet available. Validation and dry-run are available today. See the capability status page for the current operational state. The original (incorrect) text is preserved below for the record.

Archived — original entry text (incorrect): 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.

Building with an LLM? Read llms.txt for agent-oriented integration guidance.