Skip to content
Apier

Apier.no

Knowledge Catalog

Structured, source-verified topics on Norwegian compliance — what an agent needs to know about a subject before it acts. Every page renders the same canonical record the JSON API serves at /api/knowledge.

  • Altinn 3 System Users

    An Altinn 3 System User is a non-human actor an organization registers in Altinn so that other organizations can grant it rights. It authenticates with a Maskinporten access token issued for the integrating organization; authority comes from a delegation the target organization explicitly granted in advance, with no human identity in the loop at request time.

    altinn-system-user · Verified 2026-05-09 · Digitaliseringsdirektoratet / Altinn

  • Maskinporten machine-to-machine authentication

    Maskinporten is Digdir's OAuth2 service for machine-to-machine access to Norwegian government APIs. A client authenticates by signing a JWS assertion with its organization's certificate-backed keypair and receives a short-lived, scope-bound access token that identifies the calling organization rather than a human session.

    maskinporten · Verified 2026-05-19 · Digitaliseringsdirektoratet

  • Altinn vs Maskinporten: which does what

    Maskinporten answers WHICH organization's software is calling — it issues short-lived OAuth2 tokens that authenticate the calling organization. Altinn 3 System Users answer ON WHOSE BEHALF that software may act — a delegation model where a target company grants rights to a registered non-human actor. Delegated actions need both: a Maskinporten token to authenticate, and an Altinn delegation to authorize.

    altinn-vs-maskinporten · Verified 2026-05-19 · Digitaliseringsdirektoratet / Altinn

  • Authenticating against the Apier API

    Apier has three auth modes: none (Category A public infrastructure — obligations templates, deadlines, tools, capabilities), api_key (a consumer Bearer key, required for company data even on the Free tier), and admin_api_key (operator secret). Underneath, government authentication (Maskinporten, Altinn) is held server-side by Apier and never exposed to the caller.

    authentication-overview · Verified 2026-07-18 · Apier

  • Looking up and verifying a Norwegian company

    Every registered Norwegian entity has a unique 9-digit organisasjonsnummer, and its official registration record is public via Brønnøysundregistrene (the Brønnøysund Register Centre) at brreg.no. A full verification check covers registration status, bankruptcy or dissolution flags, filed annual accounts, and VAT registration.

    brreg-company-search · Verified 2026-06-28 · Brønnøysundregistrene

  • Signature rights: signaturrett and prokura

    Who can legally bind a Norwegian company is recorded as signaturrett and prokura in Brønnøysundregistrene and is viewable at brreg.no. Signaturrett binds the company generally; prokura is a narrower authority for day-to-day business that cannot sell or mortgage the company's real property without special authority.

    signature-rights · Verified 2026-06-28 · Brønnøysundregistrene

  • Norwegian company annual accounts (årsregnskap)

    A Norwegian company's annual accounts (årsregnskap) are public. They are searched, viewed, or ordered from the Register of Company Accounts (Regnskapsregisteret) at brreg.no, and include the profit and loss statement, balance sheet, notes, and the directors' report.

    annual-accounts · Verified 2026-06-28 · Brønnøysundregistrene (Regnskapsregisteret)

  • Norwegian company filing deadlines

    A Norwegian company (AS) files its corporate tax return (skattemelding) electronically by 31 May. A self-employed person (ENK) also files by 31 May, while a standard wage-earner's return is due 30 April. Annual accounts (årsregnskap) must reach the Register of Company Accounts by 31 July, with a daily late fee accruing from 1 August.

    corporate-tax-deadline · Verified 2026-06-28 · Skatteetaten

  • MVA (VAT) filing workflow

    MVA (merverdiavgift, Norwegian VAT) filing through Apier runs in four steps: discover the company's MVA obligation, dry-run the submission to validate the payload without submitting, mint a single-use human-approved token, and submit. Obligation discovery and dry-run validation are available today; live submission is gated pending Maskinporten production validation and Altinn scope approval.

    mva-filing · Verified 2026-05-25 · Skatteetaten

  • Testing against the Apier sandbox

    The Apier sandbox mirrors the production API surface under /api/v1/sandbox/* using synthetic fixtures only — it never makes a network call to any government upstream, so a sandbox 'filing' is a local state transition and nothing binding ever leaves the system. Every sandbox response carries _meta.is_sandbox: true.

    sandbox-testing · Verified 2026-07-18 · Apier (synthetic sandbox surface)

  • Troubleshooting auth errors and the structured error envelope

    Every Apier 4xx/5xx response carries the same structured envelope — { success: false, error_code, explanation, _meta } — so agents handle failures programmatically without string-matching. A 401 means the request never authenticated: a missing, malformed, revoked, or unknown key; authorization failures (missing delegation, missing scope) surface as their own codes.

    error-401-troubleshooting · Verified 2026-05-25 · Apier

  • The Apier MCP server

    Apier exposes its Norwegian-compliance surface to AI agents over Model Context Protocol at POST /api/mcp — 25 versioned tools, no custom wrapper to build. Company-data read tools are live against Brønnøysund data; billing reads use Apier's internal pricing and credit data. The sandbox-only submit_vat_return models a VAT return; the Fullmakt delegation writes broker scoped authority through an Altinn systembruker (mock-adapter-backed pending live partner validation).

    mcp-server-overview · Verified 2026-06-28 · Apier / Model Context Protocol