Skip to content
Apier.no

Capability Status

The live operational state of every Apier capability: production, dry-run only, gated, or on the roadmap.

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

Last verified: 2026-10-21

This page reflects the current operational state of every Apier capability. It exists so you can tell, before you start building, what is generally available, what validates but cannot yet submit for real, and what is built but still behind an approval gate. We would rather you know up front than discover a gate in production.

For programmatic use, GET /api/v1/capabilities now returns a machine-readable status field (live / gated / dry-run / withdrawn) on every capability and is the authoritative source of operational status for machine consumers; this hand-maintained matrix is for humans and may lag the API.

How to read this

  • 🟢 Production: live, with real data and real government calls.
  • 🟡 Dry-run only: the endpoint exists and validation works, but no live submission happens yet.
  • ⚪ Gated: built, but requires additional approval or scope before it is enabled.
  • 🔵 Pipeline: planned and not yet built.
  • ⚫ Withdrawn: the route stays published for compatibility but every call answers HTTP 410 CAPABILITY_WITHDRAWN; nothing behind it runs.

Capability matrix

Capability matrix
CapabilityEndpointStatusNotes
Company Summary/api/v1/company/{org}/summary🟢 Production—
Company Context (Tier 1)/api/v1/company/{org}/context🟢 Production—
Obligation Evaluation/api/v1/company/{org}/obligations🟢 Production—
Deadline Engine/api/v1/company/{org}/deadlines🟢 Production—
Compliance Explainer/api/v1/explain🟢 Production—
Public Deadlines/api/v1/public/deadlines🟢 ProductionNo API key required.
Public Obligations/api/v1/public/obligations🟢 ProductionNo API key required.
Exchange Rate/api/v1/tools/exchange-rate🟢 Production—
Altinn Migration Bridge/api/v1/tools/altinn-migration🟢 Production—
Capabilities/api/v1/capabilities🟢 ProductionMachine-readable capability listing.
MCP Server@apier-no/mcp🟢 ProductionPublished on npm.
Consumer Auth / Keys/api/v1/admin/keys🟢 Production—
Provenance Log_meta on all responses🟢 ProductionResponse provenance on every API response.
Sandbox/sandbox🟢 ProductionSimulates failures for agent testing.
DSR Endpoint/api/v1/privacy/dsr🟢 ProductionData-subject request handling.
Filing Validation/api/v1/actions/execute?dry_run=true⚫ WithdrawnAnswers HTTP 410 CAPABILITY_WITHDRAWN since 2026-10-21: two of its five checks read Altinn delegation state, which Apier no longer reads.
Maskinporten Authinternal — token exchange🟡 Dry-run onlyApier's own production client is registered and kept for Apier's own reads; it makes no Altinn Autorisasjon call and is never offered as a service. See what "verified" means below.
Live Filing Submission/api/v1/actions/execute⚫ WithdrawnParked and not offered (2026-10-21): the route and the human-approval routes under /api/v1/actions/pending/{id} answer HTTP 410 CAPABILITY_WITHDRAWN. Apier does not submit MVA returns.
Tier 2 Dataextended company fields⚪ GatedNot available: the Tier 2 fields depended on an Altinn delegation, which Apier no longer reads (2026-10-21).
Change Detection Query/api/v1/changes🟢 ProductionRequires read:changes scope. Without an entity_id filter, personal-field rows AND whole-entity company snapshots (which embed role-holder arrays) are withheld — the response flags this via personal_fields_withheld. Each row carries observation_kind.
Webhook Subscriptions/api/v1/subscriptions🟢 ProductionNeeds the subscribe:webhooks scope, which Apier grants; a key you create yourself does not carry it. v1 event: accounts.updated.
TypeScript SDK@apier-no/sdk🟢 ProductionPublished on npm at 0.1.2 (2026-11-15).
Python SDKapier-no🔵 Pipelinecoming soon — not yet published to PyPI
CLI@apier-no/cli (monorepo)⚪ GatedBuilt in the monorepo at v0.1.0; not yet published to npm.

Maskinporten: what "verified" means

Two true statements about Maskinporten are easy to confuse, so this section states both explicitly. This page is the authority; where any other page reads as broader than this, this page is correct.

What is verified. Apier holds a virksomhetssertifikat, a registered Maskinporten test client, and an uploaded RSA keypair. The client-assertion code path (building and signing the JWT that Maskinporten expects) is implemented, and an operator probe re-validates that configuration on demand.

What is not. The production Maskinporten client is kept for Apier's own reads only and holds no skatteetaten: scope. MASKINPORTEN_MODE ships as mock, so a normal request performs no token exchange against Maskinporten at all. Apier makes no call to Altinn Autorisasjon, brokers no system user or delegation for a customer, and does not submit filings: those surfaces are withdrawn (2026-10-21), exactly as the matrix above says.

Availability

This page reflects current operational state. Capabilities marked Gated or Pipeline are built or in progress but not generally available. For access, contact support@apier.no.

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