Skip to content
Apier

Apier.no

Data sources and licences

Apier reads public registers and reproduces what they hold. This page names every source, the licence it is reused under and how each licence condition is met. Every API response built from a source carries the same information as _meta.source_licence, and every MCP envelope built from one as metadata.source_licences. Sandbox responses use synthetic data and carry no source metadata.

Attribution

Inneholder data under Norsk lisens for offentlige data (NLOD) tilgjengeliggjort av Brønnøysundregistrene.

(Contains data under the Norwegian Licence for Open Government Data (NLOD) made available by Brønnøysundregistrene.) Licence text: https://data.norge.no/nlod/no/2.0.

Sources

  • Brønnøysundregistrene, Enhetsregisteret

    Company facts (name, legal form, status, addresses, NACE), role holders (board, general manager, auditor, proprietor), the update feeds for entities and roles, and the daily bulk files.

    Conditions and how they are met:
    Attribution with the licensor named (the sentence above, on every response and on this site); changes Apier makes are marked as Apier's; no suggestion of endorsement; personal data only with a lawful basis (see the privacy policy).

  • Brønnøysundregistrene, Fullmakttjenesten

    Coded signing authority (signaturrett) and procuration (prokura) per organisation, read from data.brreg.no/fullmakt.

    Conditions and how they are met:
    As for Enhetsregisteret. The coded rules are reproduced as the register holds them; Apier's classification of them is marked as Apier's.

  • Brønnøysundregistrene, Regnskapsregisteret (open tier)

    Filing status and the latest year's key figures from the open, unauthenticated key-figure tier. A temporary research API the register may close without notice; when it does not answer, Apier answers 503 UPSTREAM_UNAVAILABLE instead of a silent empty result.

    Conditions and how they are met:
    As for Enhetsregisteret.

  • Lovdata

    Current laws and central regulations, read only to detect changes in the sections the rulebook cites. Apier stores a content hash per section and never republishes law text.

    Conditions and how they are met:
    Individual laws and regulations only; no bulk download or systematic extraction; Lovdata named as source wherever law text is referred to.

  • Norges Bank

    Daily NOK exchange rates (the exchange-rate endpoint and the get_exchange_rate tool).

    Conditions and how they are met:
    Norges Bank named as source on every rate; rates reproduced unchanged.

What Apier adds or changes

Registry fields are reproduced as the register holds them. Everything else is Apier's own: verification results, the rulebook's obligations and deadlines, the classification of coded signing rules, data-tier and availability markers. Each response lists those fields in _meta.source_licence.derived_by_apier so a reader can tell the register's statement from Apier's. Apier never produces a person-centric overview of one person's roles across businesses and never mixes roles in voluntary organisations with roles in business activity.

No endorsement

Apier is an independent commercial service operated by Grov Digital. Brønnøysundregistrene, Digdir, Lovdata and Norges Bank do not endorse, recommend or market Apier, and their names are used here only to say where the data comes from (NLOD 2.0 section 6).

Removals

When Brønnøysundregistrene removes an organisation from its open data (a 410 Gone answer, or the update type «Fjernet»), Apier stops serving it at once and then purges its copy from the archive. After the purge Apier keeps a tombstone with the organisation number, the date and the reason, and the hashes of the purged snapshots (no content) so that earlier daily anchors can still be verified. Request and audit logs follow their normal retention; two of them keep fields taken from the register after the purge (the answer an MCP tool gave to a company lookup, and whether annual accounts were filed and for which year). Lookups then answer 410 ENTITY_REMOVED. Personal data in role-holder records is processed under the lawful basis described in the privacy policy.