Brønnøysundregistrene

Brønnøysundregistrene (the Brønnøysund Register Centre) is the Norwegian government agency that operates the national registers, including the Central Coordinating Register for Legal Entities (Enhetsregisteret), the Register of Company Accounts (Regnskapsregisteret) and the Register of Non-Profit Organisations (Frivillighetsregisteret). It publishes open, unauthenticated REST APIs on data.brreg.no for searching legal entities, sub-units, roles, update feeds and annual accounts, plus an authorised API for restricted data.

Brønnøysundregistrene publishes 14 API contracts indexed on the APIs.io network, including Enheter API, Frivillighetsregisteret API, Generelt API, and 11 more. Tagged areas include Government, Business Registry, Open Data, Norway, and Company Data.

The Brønnøysundregistrene catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Brønnøysundregistrene’s developer surface includes changelog, authentication, documentation, and 18 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

36.1/100 thin Agent 29/100 agent ready Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

2 published contracts

Government Business Registry Open Data Norway Company Data Public Sector Financial Statements

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 36.1/100 · thin

Contract Quality 11.7 / 19

Developer Ergonomics 3.2 / 15

Access Clarity 0.0 / 15

Operational Transparency 3.0 / 10

Contract Governance 2.0 / 9

Discoverability 5.5 / 8

Regulatory Posture 4.9 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 29/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Government & Public Sector regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/brreg-no/"><img src="https://apis.io/badge/brreg-no/card.svg" alt="Brønnøysundregistrene on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks Ask about this →

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 0.0 — up to +20.0 composite points Ask about this →
Developer Ergonomics scores 21.4 — up to +15.7 composite points Ask about this →
Contract Quality scores 62.5 — up to +9.4 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/brreg-no/apis.yml: open an issue on github.com/api-evangelist/brreg-no to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 14

Individual APIs this provider publishes, each with its own machine-readable definition.

Brønnøysundregistrene Enheter API

Operasjoner mot enhetsregisteret for hovedenheter

Brønnøysundregistrene Frivillighetsregisteret API

Operasjoner mot frivillighetsregisteret.

Brønnøysundregistrene Generelt API

Generelle endepunkt

Brønnøysundregistrene Kommuner API

Operasjoner mot kommuner i enhetsregisteret

Brønnøysundregistrene Kopi av årsregnskap API

The Kopi av årsregnskap API from Brønnøysundregistrene — 2 operation(s) for kopi av årsregnskap.

Brønnøysundregistrene Matrikkelenheter API

Operasjoner mot matrikkelenheter i enhetsregisteret

Brønnøysundregistrene Mellombalanse API

The Mellombalanse API from Brønnøysundregistrene — 2 operation(s) for mellombalanse.

Brønnøysundregistrene Oppdateringer API

Operasjoner mot opppdateringer i enhetsregisteret

Brønnøysundregistrene Organisasjonsformer API

Operasjoner mot organisasjonsformer i enhetsregisteret

Brønnøysundregistrene Partiregisteret API

Operasjoner mot partiregisteret

Brønnøysundregistrene Regnskapsregisteret API

the regnskapsregisteret API

Brønnøysundregistrene Roller API

Noen endepunkt for uthenting av roller er beskyttet av autentisering mot maskinporten. ### Scopes Ulike endepunkter krever ulike scopes: #### Rolleutskrift-endepunktet Endepunkt...

Brønnøysundregistrene Statistikk API

the statistikk API

Brønnøysundregistrene Underenheter API

Operasjoner mot enhetsregisteret for underenheter

Scroll for all 14

Brønnøysundregistrene API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Brønnøysundregistrene Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Brønnøysundregistrene Rate Limits

0 limits

RATE LIMITS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Brreg No Context

90 classes · 225 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Brønnøysundregistrene API Rules

57 rules · 44 error-severity 10 warn-severity 3 info-severity

SPECTRAL

OpenAPI Overlays 2

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Brønnøysundregistrene Enheter Api Certification Overlay

1 action · security · brreg-no-enheter-api-openapi.yml

DERIVED

Brønnøysundregistrene Underenheter Api Certification Overlay

1 action · security · brreg-no-underenheter-api-openapi.yml

DERIVED

JSON Schema 9

Standalone JSON Schema definitions for this provider's data models.

Enhet

64 properties

JSON SCHEMA

Mellombalanse

2 properties

JSON SCHEMA

OppdateringerEnheter

3 properties

JSON SCHEMA

OppdateringerUnderenheter

3 properties

JSON SCHEMA

Regnskap

14 properties

JSON SCHEMA

Root

1 properties

JSON SCHEMA

StreamingResponseBody

0 properties

JSON SCHEMA

Underenhet

30 properties

JSON SCHEMA

Underenheter

3 properties

JSON SCHEMA

Scroll for all 9

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Brønnøysundregistrene Authentication

http · 1 scheme

SECURITY

Brønnøysundregistrene Domain Security

TLSv1.2 · DNSSEC · DMARC

SECURITY

Brønnøysundregistrene Vulnerability Disclosure

security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Brønnøysundregistrene Scopes

1 scope

1 scopes

SCOPES

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

Brønnøysundregistrene Agentic Access

49 operations · 1 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

WellKnown

WellKnown

Design & Contract 8

Pagination, idempotency, versioning, errors, and events

Conventions

Lifecycle

Spectral

JSONLD

Vocabulary

DataModel

ErrorCatalog

Conformance

Scroll for all 8

Access & Security 6

Authentication, authorization, and security posture

OAuthScopes

Security

SecurityTxt

Authentication

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

ChangeLog

ChangeLog

Deprecation

Deprecation

Company 1

The organization behind the API

Website

Website

Other 1

Properties that don't map to a standard resource type

Hosts

Hosts

Source (apis.yml)

aid: brreg-no
name: Brønnøysundregistrene
description: Brønnøysundregistrene (the Brønnøysund Register Centre) is the Norwegian government agency that operates the
  national registers, including the Central Coordinating Register for Legal Entities (Enhetsregisteret), the Register of Company
  Accounts (Regnskapsregisteret) and the Register of Non-Profit Organisations (Frivillighetsregisteret). It publishes open,
  unauthenticated REST APIs on data.brreg.no for searching legal entities, sub-units, roles, update feeds and annual accounts,
  plus an authorised API for restricted data.
url: https://artifacts.apis.io/brreg-no/apis.yml
x-type: company
x-source: harvest:eu-gov-keynote-2026-11-10
x-tier: profiled
x-tier-reason: enrichment pass 2026-11-10 (local-v6; was harvest)
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-13'
  method: derived
specificationVersion: '0.20'
created: '2026-11-10'
modified: '2026-11-10'
tags:
- Government
- Business Registry
- Open Data
- Norway
- Company Data
- Public Sector
- Financial Statements
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: ChangeLog
  url: changelog/brreg-no-changelog.yml
- type: Conventions
  url: conventions/brreg-no-conventions.yml
- type: OAuthScopes
  url: scopes/brreg-no-scopes.yml
- type: Deprecation
  url: https://data.brreg.no/enhetsregisteret/api/docs/index.html#section/Versjonering
- type: Lifecycle
  url: lifecycle/brreg-no-lifecycle.yml
- type: AgenticAccess
  url: agentic-access/brreg-no-agentic-access.yml
- type: Spectral
  url: rules/brreg-no-rules.yml
- type: JSONLD
  url: json-ld/brreg-no-context.jsonld
- type: Vocabulary
  url: vocabulary/brreg-no-vocabulary.yml
- type: DataModel
  url: data-model/brreg-no-data-model.yml
- type: Security
  url: security/brreg-no-vulnerability-disclosure.yml
- type: ErrorCatalog
  url: errors/brreg-no-problem-types.yml
- type: Conformance
  url: conformance/brreg-no-conformance.yml
- type: SecurityTxt
  url: well-known/brreg-no-security.txt
- type: WellKnown
  url: well-known/brreg-no-well-known.yml
- type: Hosts
  url: hosts/brreg-no-hosts.yml
- type: Authentication
  url: authentication/brreg-no-authentication.yml
- type: Website
  url: https://www.brreg.no/
- type: VulnerabilityDisclosure
  url: security/brreg-no-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/brreg-no-domain-security.yml
- type: Documentation
  url: https://data.brreg.no/enhetsregisteret/api/docs/index.html
apis:
- aid: brreg-no:brreg-no-enheter-api
  name: Brønnøysundregistrene Enheter API
  description: Operasjoner mot enhetsregisteret for hovedenheter
  humanURL: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  baseURL: https://data.brreg.no
  tags:
  - enheter
  properties:
  - type: OpenAPI
    url: openapi/brreg-no-enheter-api-openapi.yml
  - type: Documentation
    url: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  - type: Documentation
    url: https://data.brreg.no/regnskapsregisteret/regnskap/swagger-ui/index.html
  - type: JSONSchema
    url: json-schema/brreg-no-enhet-schema.json
- aid: brreg-no:brreg-no-frivillighetsregisteret-api
  name: Brønnøysundregistrene Frivillighetsregisteret API
  description: Operasjoner mot frivillighetsregisteret.
  humanURL: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  baseURL: https://data.brreg.no
  tags:
  - frivillighetsregisteret
  properties:
  - type: OpenAPI
    url: openapi/brreg-no-frivillighetsregisteret-api-openapi.yml
  - type: Documentation
    url: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  - type: Documentation
    url: https://data.brreg.no/regnskapsregisteret/regnskap/swagger-ui/index.html
- aid: brreg-no:brreg-no-generelt-api
  name: Brønnøysundregistrene Generelt API
  description: Generelle endepunkt
  humanURL: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  baseURL: https://data.brreg.no
  tags:
  - generelt
  properties:
  - type: OpenAPI
    url: openapi/brreg-no-generelt-api-openapi.yml
  - type: Documentation
    url: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  - type: Documentation
    url: https://data.brreg.no/regnskapsregisteret/regnskap/swagger-ui/index.html
  - type: JSONSchema
    url: json-schema/brreg-no-root-schema.json
- aid: brreg-no:brreg-no-kommuner-api
  name: Brønnøysundregistrene Kommuner API
  description: Operasjoner mot kommuner i enhetsregisteret
  humanURL: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  baseURL: https://data.brreg.no
  tags:
  - kommuner
  properties:
  - type: OpenAPI
    url: openapi/brreg-no-kommuner-api-openapi.yml
  - type: Documentation
    url: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  - type: Documentation
    url: https://data.brreg.no/regnskapsregisteret/regnskap/swagger-ui/index.html
- aid: brreg-no:brreg-no-kopi-av-rsregnskap-api
  name: Brønnøysundregistrene Kopi av årsregnskap API
  description: The Kopi av årsregnskap API from Brønnøysundregistrene — 2 operation(s) for kopi av årsregnskap.
  humanURL: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  baseURL: https://data.brreg.no
  tags:
  - Kopi av årsregnskap
  properties:
  - type: OpenAPI
    url: openapi/brreg-no-kopi-av-rsregnskap-api-openapi.yml
  - type: Documentation
    url: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  - type: Documentation
    url: https://data.brreg.no/regnskapsregisteret/regnskap/swagger-ui/index.html
  - type: JSONSchema
    url: json-schema/brreg-no-streaming-response-body-schema.json
- aid: brreg-no:brreg-no-matrikkelenheter-api
  name: Brønnøysundregistrene Matrikkelenheter API
  description: Operasjoner mot matrikkelenheter i enhetsregisteret
  humanURL: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  baseURL: https://data.brreg.no
  tags:
  - matrikkelenheter
  properties:
  - type: OpenAPI
    url: openapi/brreg-no-matrikkelenheter-api-openapi.yml
  - type: Documentation
    url: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  - type: Documentation
    url: https://data.brreg.no/regnskapsregisteret/regnskap/swagger-ui/index.html
- aid: brreg-no:brreg-no-mellombalanse-api
  name: Brønnøysundregistrene Mellombalanse API
  description: The Mellombalanse API from Brønnøysundregistrene — 2 operation(s) for mellombalanse.
  humanURL: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  baseURL: https://data.brreg.no
  tags:
  - Mellombalanse
  properties:
  - type: OpenAPI
    url: openapi/brreg-no-mellombalanse-api-openapi.yml
  - type: Documentation
    url: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  - type: Documentation
    url: https://data.brreg.no/regnskapsregisteret/regnskap/swagger-ui/index.html
  - type: JSONSchema
    url: json-schema/brreg-no-mellombalanse-schema.json
  - type: JSONSchema
    url: json-schema/brreg-no-streaming-response-body-schema.json
- aid: brreg-no:brreg-no-oppdateringer-api
  name: Brønnøysundregistrene Oppdateringer API
  description: Operasjoner mot opppdateringer i enhetsregisteret
  humanURL: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  baseURL: https://data.brreg.no
  tags:
  - oppdateringer
  properties:
  - type: OpenAPI
    url: openapi/brreg-no-oppdateringer-api-openapi.yml
  - type: Documentation
    url: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  - type: Documentation
    url: https://data.brreg.no/regnskapsregisteret/regnskap/swagger-ui/index.html
  - type: JSONSchema
    url: json-schema/brreg-no-oppdateringer-underenheter-schema.json
  - type: JSONSchema
    url: json-schema/brreg-no-oppdateringer-enheter-schema.json
- aid: brreg-no:brreg-no-organisasjonsformer-api
  name: Brønnøysundregistrene Organisasjonsformer API
  description: Operasjoner mot organisasjonsformer i enhetsregisteret
  humanURL: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  baseURL: https://data.brreg.no
  tags:
  - organisasjonsformer
  properties:
  - type: OpenAPI
    url: openapi/brreg-no-organisasjonsformer-api-openapi.yml
  - type: Documentation
    url: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  - type: Documentation
    url: https://data.brreg.no/regnskapsregisteret/regnskap/swagger-ui/index.html
- aid: brreg-no:brreg-no-partiregisteret-api
  name: Brønnøysundregistrene Partiregisteret API
  description: Operasjoner mot partiregisteret
  humanURL: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  baseURL: https://data.brreg.no
  tags:
  - partiregisteret
  properties:
  - type: OpenAPI
    url: openapi/brreg-no-partiregisteret-api-openapi.yml
  - type: Documentation
    url: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  - type: Documentation
    url: https://data.brreg.no/regnskapsregisteret/regnskap/swagger-ui/index.html
- aid: brreg-no:brreg-no-regnskapsregisteret-api
  name: Brønnøysundregistrene Regnskapsregisteret API
  description: the regnskapsregisteret API
  humanURL: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  baseURL: https://data.brreg.no
  tags:
  - regnskapsregisteret
  properties:
  - type: OpenAPI
    url: openapi/brreg-no-regnskapsregisteret-api-openapi.yml
  - type: Documentation
    url: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  - type: Documentation
    url: https://data.brreg.no/regnskapsregisteret/regnskap/swagger-ui/index.html
  - type: JSONSchema
    url: json-schema/brreg-no-regnskap-schema.json
- aid: brreg-no:brreg-no-roller-api
  name: Brønnøysundregistrene Roller API
  description: "Noen endepunkt for uthenting av roller er beskyttet av autentisering mot maskinporten.\n\n### Scopes\n\nUlike\
    \ endepunkter krever ulike scopes:\n\n#### Rolleutskrift-endepunktet\nEndepunktet [/autorisert-api/personer/rolleutskrift](#tag/roller/operation/hentRolleutskriftForPerson)\
    \ krever scopet:\n- `brreg:data:enhetsregisteret:roller:person:oppslag:fnr`\n\nAlle offentlige og private virksomheter\
    \ kan søke om tilgang.   \n\n#### Roller-endepunkter med fødselsnummer for private aktører \n\nEndepunktene [/autorisert-api/enheter/{orgnr}/roller](#tag/roller/operation/hentRollerMedFnr)\
    \ og [/autorisert-api/roller/totalbestand](#tag/roller/operation/lastnedRollerTotalbestandMedPid) krever scopet: \n\n\
    - `brreg:data:enhetsregisteret:roller` \n\nKredittopplysningsforetak og finansforetak kan søke om tilgang. \n\n#### Roller-endepunkter\
    \ med fødselsnummer for offentlige aktører \n\nEndepunktene [/autorisert-api/enheter/{orgnr}/roller](#tag/roller/operation/hentRollerMedFnr)\
    \ og [/autorisert-api/roller/totalbestand](#tag/roller/operation/lastnedRollerTotalbestandMedPid) krever scopet: \n\n\
    - `brreg:data:enhetsregisteret:auto:roller`\n\nOffentlig sektor (STAT, KOMM, FYLK, ORGL og ADOS) har automatisk tilgang\
    \ til scopet. \n\n### Søke om tilgang \n\nSende en epost til opendata@brreg.no med følgende info: \n- organisasjonsnummer\
    \  \n- navn på virksomheten  \n- hvilket scope man ønsker tilgang til\n\n### Autentisering\n\nHusk at selv om du har fått\
    \ rettigheten til å bruke ett av scopene, så må du også legge scopet til din egen klient i maskinporten. \n\n[Les her](https://docs.digdir.no/docs/Maskinporten/maskinporten_virksomhetssertifikat#autentiseringsmetoder-i-maskinporten)\
    \ hvordan man kan autentisere seg med maskinporten. \n\nKall mot apiet for uthenting av roller med fødselsnummer krever\
    \ at du sender inn en JWT signert med en av de to autentiseringsmåtene beskrevet i linken ovenfor.\nDu må også sette resource\
    \ claim i JWT grant til `https://data.brreg.no/enhetsregisteret/autorisert-api` før man signerer den og sender over til\
    \ https://maskinporten.no. I preprod-miljøet må denne settes til `https://data.ppe.brreg.no/enhetsregisteret/autorisert-api`.\
    \ Når man skal bruke preprod-miljøet så må man bruke `https://test.maskinporten.no` for å lage token.\nBearer token må\
    \ være en JWT signert av enten virksomhetssertifikat eller assymetrisk nøkkel.\n\n### Eksempel\n\n```bash\ncurl -v -X\
    \ GET -H \"Authorization: Bearer $SIGNED_JWT_TOKEN\" \\\n    https://data.brreg.no/enhetsregisteret/autorisert-api/enheter/123456789/roller\n\
    ```"
  humanURL: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  baseURL: https://data.brreg.no
  tags:
  - roller
  properties:
  - type: OpenAPI
    url: openapi/brreg-no-roller-api-openapi.yml
  - type: Documentation
    url: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  - type: Documentation
    url: https://data.brreg.no/regnskapsregisteret/regnskap/swagger-ui/index.html
- aid: brreg-no:brreg-no-statistikk-api
  name: Brønnøysundregistrene Statistikk API
  description: the statistikk API
  humanURL: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  baseURL: https://data.brreg.no
  tags:
  - statistikk
  properties:
  - type: OpenAPI
    url: openapi/brreg-no-statistikk-api-openapi.yml
  - type: Documentation
    url: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  - type: Documentation
    url: https://data.brreg.no/regnskapsregisteret/regnskap/swagger-ui/index.html
- aid: brreg-no:brreg-no-underenheter-api
  name: Brønnøysundregistrene Underenheter API
  description: Operasjoner mot enhetsregisteret for underenheter
  humanURL: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  baseURL: https://data.brreg.no
  tags:
  - underenheter
  properties:
  - type: OpenAPI
    url: openapi/brreg-no-underenheter-api-openapi.yml
  - type: Documentation
    url: https://data.brreg.no/enhetsregisteret/api/docs/index.html
  - type: Documentation
    url: https://data.brreg.no/regnskapsregisteret/regnskap/swagger-ui/index.html
  - type: JSONSchema
    url: json-schema/brreg-no-underenhet-schema.json
  - type: JSONSchema
    url: json-schema/brreg-no-underenheter-schema.json
x-enrichment:
  date: '2026-11-10'
  status: enriched
  artifacts_added: 20
  pass: local-v6

Brønnøysundregistrene API — frequently asked questions

Does Brønnøysundregistrene have an API?

Yes. APIs.io lists 14 APIs from Brønnøysundregistrene, including Brønnøysundregistrene Enheter API, Brønnøysundregistrene Frivillighetsregisteret API and Brønnøysundregistrene Generelt API, and 11 more.

Is there an OpenAPI specification for the Brønnøysundregistrene API?

Yes. APIs.io indexes 14 OpenAPI specifications for Brønnøysundregistrene, each linked for download from this page.

How do I authenticate with the Brønnøysundregistrene API?

Brønnøysundregistrene uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Brønnøysundregistrene Authentication.

Is the Brønnøysundregistrene API ready for AI agents?

Brønnøysundregistrene has a Kin Score of 36.1 out of 100 (thin) and an Agent Readiness score of 28.6 (agent-ready), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/brreg-no"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/brreg-no/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/brreg-no/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.