Norway Company & Supplier Evidence

This actor produces bounded, receipt-backed company evidence from the official Brønnøysund Register Centre (Brønnøysundregistrene) Central Coordinating Register for Legal Entities (Enhetsregisteret). No API key is required.

The strongest route is an exact nine-digit organisation number. Name queries use the official bounded navn search with navnMetodeForSoek=FORTLOEPENDE; the actor never silently chooses among multiple or non-exact candidates.

Official sources and rights

• Entity Register API v2 documentation: https://data.brreg.no/enhetsregisteret/api/dokumentasjon/en/index.html
• Entity endpoint: https://data.brreg.no/enhetsregisteret/api/enheter
• Norwegian Licence for Open Government Data (NLOD) 2.0: https://data.norge.no/nlod/en/2.0

The official documentation identifies the data as NLOD-licensed and documents the versioned entity media type application/vnd.brreg.enhetsregisteret.enhet.v2+json. NLOD 2.0 permits copying, use, modification, and distribution subject to its terms. It requires attribution and, where practical, links to the source and licence. Changed information must be identified as changed. It also excludes personal data where there is no lawful basis for disclosure and further processing.

Every result carries this attribution and change disclosure:

Contains data under the Norwegian licence for Open Government Data (NLOD) distributed by Brønnøysundregistrene. CivicDataForge changed the information by selecting and minimizing fields and using stable English keys; Norwegian source strings were not translated.

Privacy-minimized product boundary

This actor calls only /api/enheter and /api/enheter/{organisasjonsnummer}. It does not call public or Maskinporten-protected role endpoints.

It deliberately excludes:

• natural-person roles and personal identification numbers
• email, telephone, and mobile fields
• street address lines
• source _links

Business and postal addresses are reduced to country, postal code/city, and municipality. Entity legal names and historical entity names remain because they are identity evidence published on the entity endpoint, but consumers remain responsible for an appropriate legal basis for any processing that concerns a natural person.

Input

{
  "batchReference": "supplier-intake-2026-08-23",
  "maxRecords": 10,
  "queries": [
    {
      "reference": "supplier-001",
      "organisationNumber": "974760673",
      "name": "REGISTERENHETEN I BRØNNØYSUND",
      "purpose": "SUPPLIER_ONBOARDING_EVIDENCE"
    },
    {
      "reference": "name-discovery",
      "name": "REGISTERENHETEN I BRØNNØYSUND",
      "purpose": "ENTITY_VERIFICATION"
    }
  ]
}

purpose is caller-declared context and must be one of:

• ENTITY_VERIFICATION
• SUPPLIER_ONBOARDING_EVIDENCE
• PROCUREMENT_RESEARCH
• OTHER

It is recorded in the receipt but never changes source facts or produces an eligibility verdict. maxRecords is 1–50. A name request asks the official service for maxRecords + 1 candidates so truncation is detected before only maxRecords are returned.

When organisation number and name are both supplied, the organisation number controls the exact lookup and the name is only a consistency check. A name conflict does not override the exact record; it is disclosed for review.

Decisions

• MATCH: an exact organisation-number endpoint returned the requested entity, or a bounded name search reported exactly one candidate whose current name equals the submitted name after conservative Unicode/case/punctuation normalization.
• NO_PUBLISHED_MATCH: the exact endpoint returned the documented 404, or a complete bounded name search reported zero candidates.
• AMBIGUOUS: a name search did not establish one unique exact current-name candidate. Candidate records and truncation state are preserved.
• SOURCE_UNAVAILABLE: timeout, non-JSON response, unsafe redirect, HTTP/source failure, size breach, or malformed source structure. It is never converted into a no-match.
• INVALID_INPUT: missing/invalid purpose, malformed nine-digit number, empty/oversized name, invalid bounds, or invalid previous receipts. Invalid queries cause no source request.

Evidence and receipts

Norwegian publisher strings such as organisation-form, industry, activity, and statutory-purpose descriptions are preserved with _no keys. They are not machine translated. Stable English keys describe field meaning only.

Each row includes:

• exact official source_url and retrieved_at
• raw-response source_response_sha256
• a pinned source_schema_fingerprint over media type, selected mappings, and explicit exclusions
• normalized records with deterministic record_receipt_hash
• deterministic query decision_receipt_hash
• shared deterministic batch_receipt_hash
• NLOD 2.0 rights, source, attribution, and change disclosure
• explicit scope completeness and privacy-minimization state

Retrieval timestamps remain observable metadata but are excluded from deterministic receipt payloads.

Non-verdict boundary

Published registry status fields—including bankruptcy or liquidation fields—are copied as dated source facts. CivicDataForge does not interpret them as KYC, supplier acceptance, procurement qualification, sanctions, solvency, credit, or legal eligibility decisions. All verdict flags remain false.

The official source and NLOD terms provide the data “as is” without data-quality or availability warranties. Consumers should read the current official record and applicable law before consequential action.

Local verification

npm install
npm test
npm run test:live
npm run test:actor
npm audit --omit=dev --audit-level=high
npm pack --dry-run --json

The offline suite covers every decision, exact/name route construction, ambiguity/truncation, response validation, unsafe redirects, oversize responses, invalid inputs, PII minimization, Norwegian-string preservation, and deterministic receipts. Live tests remain bounded to one exact organisation and one synthetic no-result name.