---
title: "Resolve a Norwegian organisasjonsnummer to a structured company profile"
method: POST
path: "/api/v1/brreg/company-profile"
tags: ["Brreg"]
---

# Resolve a Norwegian organisasjonsnummer to a structured company profile

`POST /api/v1/brreg/company-profile`

## Request

- Base URL: `https://www.apier.no`
- URL: `https://www.apier.no/api/v1/brreg/company-profile`
- Auth: HTTP bearer

Given a 9-digit Norwegian organisasjonsnummer, returns a structured company profile sourced from Brønnøysund Enhetsregisteret (data.brreg.no). The agent-facing response carries the company's display name, organisational form (e.g. AS — Aksjeselskap, ENK — Enkeltpersonforetak, ASA — Allmennaksjeselskap), Norwegian industry codes (NACE) with descriptions, the registered street address (forretningsadresse), any separate business address (postadresse), the Enhetsregisteret registration date, the agent-facing status enum (`active` for operating entities, `dissolved` for deleted/bankrupt/liquidating entities), the dissolution date when known (slettedato → dissolved_at), the MVA-registered flag (registrertIMvaregisteret), and a deduplicated list of role codes assigned to natural persons (DAGL, LEDE, MEDL, NESTL, INNH, etc.). The response carries role codes ONLY — never personal identifiers (fødselsdato, personnummer, home address, email, phone). Two-layer PII defense is enforced: the parser declares an explicit allowlist (LAYER 1) and runs a recursive deep-scan with fnr-shape regex (LAYER 2) before any value reaches the response, the cache row, the audit_log, the company_delta_log, or the changes archive. Cache TTL is 24 hours; if Brønnøysund is unavailable, the response may serve a stale cached row up to 7 days old with `metadata.stale=true` and `metadata.staleness_seconds` populated. Beyond the 7-day ceiling we 503 UPSTREAM_UNAVAILABLE (silently serving older data would mislead agents). The data is Tier 1 public infrastructure under NLOD (Norsk lisens for offentlige data); no delegation is required. Required scope: `read:brreg`. The MCP tool `get_company_profile` proxies through this endpoint via the registry pattern — REST and MCP callers share one source of truth. This is the one metered POST, so it honours the `Idempotency-Key` header: a retry carrying the same key and body is answered from the cached first response with `Idempotent-Replay: true` and is NOT debited a second time — the replay short-circuits before the credit check. Without the header every call is an independent metered read.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `org_number` string, required: 9-digit Norwegian organisasjonsnummer. Validated for shape via the regex AND for mod-11 checksum after Zod (failures return distinct error codes: VALIDATION_FAILED for shape, ORG_NUMBER_INVALID_CHECKSUM for mod-11).

## Response `200`

Company profile resolved. The response wraps the agent envelope under `data` (the standard /api/v1/* `{ success, data, _meta }` shape; the MCP executor exposes `data` as the top-level `{ result, justification, metadata }` envelope to MCP callers).

- object
  - `success` true, required
  - `data` object, required
    - `result` object, required
      - `org_number` string, required
      - `name` string, required
      - `org_form` object, required
        - `code` string, required: Brreg organisasjonsform.kode (e.g. AS, ENK, ASA)
        - `label` string, required: Brreg organisasjonsform.beskrivelse (e.g. Aksjeselskap)
      - `nace_codes` object[], required: Sorted by code asc (determinism). Both `code` and `description` reflect Brreg's beskrivelse — descriptions are persisted in a dedicated `nace_descriptions` JSONB column so cache-hit responses match cache-miss responses for the same org. Description may be the empty string only for codes that pre-date the nace_descriptions column (rare: rows seeded before).
        - `code` string, required
        - `description` string, required
      - `registered_address` object, nullable, required: Brreg `forretningsadresse` — null when the company has no registered address (rare; some legacy entities).
        - `street` string, required: Joined street-line array (e.g. 'Storgata 1, 2. etasje').
        - `postal_code` string, required
        - `postal_city` string, required
        - `country` string, required: Brreg's `land` field, defaults to 'Norge' when not present.
      - `business_address` object, nullable, required: Brreg `postadresse` — null when no separate postal address is registered. clarification: null DOES NOT mean 'equals registered_address'; agents that need a single 'where to send mail' value should fall back to registered_address explicitly when this is null.
        - `street` string, required
        - `postal_code` string, required
        - `postal_city` string, required
        - `country` string, required
      - `registration_date` string, date, nullable, required
      - `status` 'active' | 'dissolved', required
      - `dissolved_at` string, date, nullable, required
      - `mva_registered` boolean, nullable, required: Tier 1 — VAT (MVA) registration status from Brønnøysund's `registrertIMvaregisteret`. Tri-state: `true` = registered, `false` = not registered, `null` = unknown (BRREG omitted the field, or the cached company row has no value yet). Never coerced `null` → `false` — matches the `/context`, `/summary`, and `/verify` contracts.
      - `key_people` object[], required: Sorted by role_code asc. Each entry is role-shaped only — `person_role_only:true` is the schema-level affirmation that no personal identifier is present.
        - `role_code` string, required
        - `role_label` string, required
        - `person_role_only` true, required
    - `justification` object, required
      - `source` 'brreg', required
      - `source_url` string, uri, required
      - `fetched_at` string, date-time, required
      - `legal_basis` 'NLOD — Norsk lisens for offentlige data', required
      - `data_freshness` string, date-time, required
    - `metadata` object, required
      - `correlation_id` string, uuid, required
      - `cached` boolean, required
      - `stale` boolean, required: True only on the stale-cache fallback path (Brreg upstream unavailable, cached row within 7-day ceiling).
      - `staleness_seconds` integer: Present iff stale=true.
  - `_meta` TrustMetadata, required: Metadata included in every response for trust and verifiability.
    - `rulebook_version` string, required: Current Rulebook version. Internal rule-version records carry structured origin metadata (`initial_seed` | `human_review` | `lovdata_drift_response` | `audit_finding` | `customer_question` | `legal_correction`) for operator forensics, but that attribution is deliberately NOT exposed on public responses to avoid leaking operational signal.
    - `data_freshness` string, date-time, required: When this data was last fetched (ISO 8601 UTC).
    - `last_verified` string, date-time, required: When this data was last verified against source (ISO 8601 UTC).
    - `source` string, required: Origin of this data. Defaults to `apier.no`. The agent-readiness probe (`GET /api/v1/health/agent-readiness`) is the one surface that may instead emit `apier.no telemetry` — it does so when at least one of its endpoint rates came from measured live telemetry, and falls back to `apier.no` when every rate is a static default; all other endpoints always emit `apier.no`.
    - `data_source` string: Authoritative origin of the underlying data (listed alongside rulebook_version, data_freshness, last_verified, legal_basis for Rulebook-influenced endpoints). Distinct from `source` (the response origin): `data_source` identifies the authoritative data publisher — e.g. 'Brønnøysund Enhetsregisteret + Apier Universal Rulebook'. Present on registry-backed endpoints.
    - `served_from` 'cache' | 'live' | 'static': Cache-aware endpoints only — 'cache' when the response was served from the local copy, 'live' when the gateway just refreshed from the upstream, 'static' when the payload was computed deterministically from pure code with no DB or upstream read (e.g. /v1/public/deadlines). Absent on endpoints that don't carry this semantic.
    - `stale` boolean: Cache-aware endpoints only — true when the upstream was unreachable and a within-limit cached row was served as a fallback. Absent on normal responses.
    - `schema_version` string, required: OpenAPI contract version at the time of the response; matches `info.version`. Always present on every `/v1/*` response so a future schema break can be traced to the exact rows / audit events that predate / postdate it. Agent-facing machine interfaces (v1/capabilities, workflows.json) may override with their own narrower surface version; all other endpoints inherit the manifest-level version.
    - `legal_basis` string: Legal basis under which the response data is reused. Present on Rulebook-influenced endpoints (v1/company/{org}/obligations, /v1/company/{org}/deadlines). Common value: 'NLOD — public registry reuse'.
    - `rule_count` integer: Rule-evaluation count — total rules evaluated for this request. Present on endpoints that invoke the Rulebook evaluator (v1/company/{org}/obligations).
    - `applicable_count` integer: Count of rules whose evaluation_result is 'applicable'. Present on evaluator endpoints.
    - `not_applicable_count` integer: Count of rules whose evaluation_result is 'not_applicable'. Present on evaluator endpoints.
    - `insufficient_data_count` integer: Count of rules whose evaluation_result is 'insufficient_data' (Tier 2 gated). Present on evaluator endpoints. rule_count = applicable_count + not_applicable_count + insufficient_data_count.
    - `cache_age_ms` integer, nullable: Cache layer: milliseconds since the cached row was computed, or null on a cache miss (served_from === 'live'). Agents use it alongside data_freshness as a staleness signal. Present on endpoints wired to the cache (v1/company/{org}/obligations, /deadlines, /summary, /v1/public/obligations, /v1/public/deadlines).
    - `response_time_ms` integer: Speed signal: total server-side processing time in milliseconds, measured via performance.now() at the route boundary. Mirrored on the `X-Apier-Response-Time-Ms` header so agents can key on it without parsing the body. Present on every endpoint.
    - `response_timestamp` string, date-time: RFC 3339 / ISO 8601 UTC timestamp stamped by the response builder at wire-exit. Mirrored on the `provenance_log.response_timestamp` column by a fire-and-forget writer. Distinct from `data_freshness` (when upstream data was fetched) and `last_verified` (when the citation was verified); this is the moment the envelope left the server. Always populated at runtime — deliberately left out of the `required` list to avoid a cascading contract change that would invalidate every pre-existing example envelope in this spec (append-only response contracts). A future revision may promote it into the `required` list alongside a bulk example refresh.
    - `response_hash` string: SHA-256 hash of the canonical-JSON form of the envelope with `_meta` stripped before hashing, prefixed with `sha256:`. Mirrored on `provenance_log.response_hash` so a consumer can independently re-hash the bytes they received and compare against what we persisted (integrity receipt). Stripping `_meta` is load-bearing: volatile fields (response_time_ms, cache_age_ms, served_from) and the hash itself would otherwise feed into the digest and break the cache-hit-bytewise-identical invariant.
    - `source_snapshot_id` string: Optional free-text pointer into an upstream sync snapshot the response derives from — e.g. a Brreg sync's `brreg-<ISO>` snapshot id. Absent when the response is not tied to a specific upstream snapshot (capabilities, tools, static deadlines).
    - `is_sandbox` true: Present and `true` only when the response was generated from sandbox fixture data (currently `ALTINN_MODE=sandbox` on `/api/v1/altinn/list-acting-capacity`). Absent (NOT `false`) on every other response — the absent-vs-false distinction is deliberate so downstream agents branching on `if (response._meta.is_sandbox)` cannot be misled into treating non-sandbox responses as positively-confirmed-not-sandbox. Distinct from the `/v1/sandbox/*` `is_sandbox: true` literal in `SandboxMeta` (which carries the sandbox surface tag); this flag rides through the production `/api/v1/altinn/*` surface to forensically tag a sandbox-mode response that an OEM evaluator received.
    - `cost_nok` number: What this call debited from the caller's prepaid credit balance, in NOK, rendered from the integer-øre ledger (50 øre → 0.5; the ledger itself never leaves whole øre and no float arithmetic touches a balance). Present on the 2xx body of every metered company-data read — the same debit that sets the `X-Credits-Cost-Ore` header, so the two never disagree. `0` when nothing was charged: credit enforcement running dark (the response then also carries `X-Credit-Check: shadow`) or the sandbox surface. Absent on unmetered endpoints and on error envelopes — a refunded 5xx/403/404 claims no cost rather than a wrong one. Lives under `_meta`, which `response_hash` excludes, so the provenance receipt is unaffected; the route's ETag is computed before the credit wrapper stamps it, so a conditional request can still short-circuit to 304. Append-only addition.
    - `wallet_remaining_nok` number, nullable: The prepaid credit balance remaining AFTER this call's debit, in NOK (same rendering as `cost_nok`; mirrors the `X-Credits-Balance-Ore` header). `null` when no balance was read: credit enforcement running dark, or the sandbox surface. Present wherever `cost_nok` is. An agent planning a sequence of metered calls can divide this by the per-call price from GET /api/v1/pricing to know how many reads remain before a 402 INSUFFICIENT_CREDITS. Append-only addition.
    - `spend_cap_remaining_nok` number: What the calling key may still spend under its tighter spend cap (Europe/Oslo calendar day or month) AFTER this call's debit, in NOK (same rendering as `cost_nok`; never below 0). Present on the 2xx body of a metered read only when credit enforcement is live AND the key has a daily or monthly cap (set with PATCH /api/v1/account/keys/{id}); absent otherwise. When it reaches 0 the next metered call on this key returns 402 SPEND_CAP_REACHED until the cap resets. Append-only addition.

## Other responses

- `400`: Validation failure. Two distinct error codes: VALIDATION_FAILED for shape (Zod regex / unknown field / wrong type) and ORG_NUMBER_INVALID_CHECKSUM for mod-11 failure. The distinct codes let agents recover differently.
- `401`: Missing or invalid API key.
- `402`: Prepaid credit balance does not cover this call. Emitted ONLY when credit enforcement is live (CREDITS_LIVE=true); while enforcement runs dark — the launch default — responses carry `X-Credit-Check: shadow` instead and a 402 is impossible. The debit is CONDITIONAL: nothing was charged for this 402. The balance is checked-and-debited atomically BEFORE the handler runs, so an insufficient balance leaves both the balance and the ledger untouched. Body is the standard Rulebook error envelope plus the machine-readable payment-recovery contract: `top_up_url` (absolute URL to the billing dashboard where a human tops up the key's prepaid balance), `balance_ore` (the observed balance at rejection time), and `cost_ore` (this call's price) — together with the catalog-derived `retryable`/`fix_hint`/`docs_url` fields, a stranded agent can compute the shortfall and self-recover from this body alone. Discover all prices without auth at GET /api/v1/pricing. Agents should surface top_up_url as a human-handover link rather than retry: with an unchanged balance the endpoint returns this 402 deterministically. The same status carries a second, distinct refusal: 402 SPEND_CAP_REACHED, when the key's own Europe/Oslo daily or monthly spend cap (set with PATCH /api/v1/account/keys/{id}) would be exceeded. It is checked inside the same atomic RPC BEFORE the debit, so it too charges nothing and writes no ledger row. Branch on `error_code`: SPEND_CAP_REACHED carries `cap`, `cap_ore`, `spent_ore`, `cost_ore` and `resets_at` plus a Retry-After header, is `retryable: true` (the identical call succeeds after `resets_at`), and carries no `top_up_url`: topping up does not lift a cap. Like INSUFFICIENT_CREDITS it occurs only while enforcement is live.
- `403`: API key lacks the required `read:brreg` scope.
- `404`: Brønnøysund returned no record for this organisasjonsnummer (404/410). Authoritative — retrying will not change the result.
- `409`: Another request with this `Idempotency-Key` is still being processed (error_code=IDEMPOTENCY_IN_PROGRESS). Only reachable when the header is sent: the one metered POST honours it so a retry after a lost response is never debited twice. Wait for the `Retry-After` seconds and retry with the same key and body.
- `422`: This Idempotency-Key was previously used with a different request body. Idempotency keys must be unique per unique request.
- `429`: Rate limit reached on at least one of TWO independent dimensions running in parallel: per-(api_key, endpoint) per-minute (the established per-tier scaling — Free / Starter / Professional / Enterprise unlimited) AND per-(api_key, org_number) per-day (bounds runaway-agent failure modes per client org so one org's traffic cannot starve siblings sharing the same key; daily bucket window is one calendar day in Europe/Oslo, DST-aware). The `X-RateLimit-Dimension` header identifies which bucket tripped: `per_key`, `per_org`, or `both` (when the same request exceeds both — the binding Retry-After is the per-org value because the per-org window is hours/days vs the per-minute window). The `Retry-After` header indicates how many seconds to wait before the binding window resets; `X-RateLimit-Limit` / `X-RateLimit-Remaining` / `X-RateLimit-Reset` describe the per-minute bucket state. The per-day per-org limits per tier (sized at ~100× typical daily volume — the dimension exists to bound failure modes, not to monetize) are: Free 1000/org/day, Starter 5000, Professional 25000, Enterprise unlimited. On rare infrastructure-side failures the gateway fails OPEN and passes the request through with `X-RateLimit-Check: skipped` on the response — clients can treat that as a transient signal that quota enforcement was briefly degraded.
- `503`: Brønnøysund is unavailable AND no fresh-enough cached row (within the 7-day ceiling) exists for this organisation. The retry guidance is in the body's `explanation.summary` text rather than a `Retry-After` header — agents should retry after roughly 60 seconds (the per-org single-flight throttle window). SECOND CAUSE, only when the request carries an `Idempotency-Key`: the idempotency reservation service is temporarily unavailable (same error_code=UPSTREAM_UNAVAILABLE). Nothing was executed and nothing was debited — the reservation runs before the credit check — so retry with the same key and body. In both causes no credit stands charged: the Brønnøysund 503 is raised inside the handler and refunded as a non-chargeable outcome, the reservation 503 never reaches the debit.

---

[API](https://skmtc.dev/apier/apis/apier-no-api.md) · [All operations](https://skmtc.dev/apier/apis/apier-no-api/llms.txt) · [OpenAPI document](https://skmtc.dev/apier/apis/apier-no-api/revisions/9ec19bc87311?raw)